Cell Configuration For Packet Duplication

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. Packet data convergence protocol (PDCP) packet duplication may be configured for a bearer of a wireless device. The bearer may use various cells to send packets. A base station central unit and/or a base station distributed unit may configure the cells for the bearer based on various types of information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit and is a continuation of U.S.application Ser. No. 16/246,110, titled “Cell Configuration for PacketDuplication” and filed on Jan. 11, 2019, which claims the benefit ofU.S. Provisional Application No. 62/616,386, titled “PDCP DuplicationCell Configuration” and filed on Jan. 11, 2018, each of which is herebyincorporated by reference in its entirety.

BACKGROUND

In wireless communications, packets may be duplicated. A base stationmay configure cells for packet duplication. Inefficient methods forconfiguring cells may lead to decreased performance of wirelesscommunications.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for configuring cellsfor packet duplication. Packet duplication may be configured for abearer of a wireless device. The bearer of the wireless device may beassociated with different cells for sending original packets and/orduplicated packets. A base station central unit and/or a base stationdistributed unit may configure the cells of the bearer of the wirelessdevice. The configuration of the cells may be based on informationassociated with the base station central unit and/or associated with thebase station distributed unit. Effective cell configuration may befacilitated, and/or performance of wireless communications may beincreased, by configuring the cells for packet duplication in anefficient manner.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing(OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for twocarriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink anddownlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA)and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in asecondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F showexamples for architectures of tight interworking between a 5G RAN and along term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocolstructures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNBdeployment.

FIG. 15 shows an example for cell configuration associated with uplinktransmissions.

FIG. 16 shows an example for cell configuration associated with downlinktransmissions.

FIG. 17 is a diagram showing an example method for cell configuration.

FIG. 18 shows another example for cell configuration associated withuplink transmissions.

FIG. 19 shows another example for cell configuration associated withdownlink transmissions.

FIG. 20 is a diagram showing another example method for cellconfiguration.

FIG. 21 shows an example method for cell configuration associated with afirst part of a base station.

FIG. 22 shows another example method for cell configuration associatedwith a first part of a base station.

FIG. 23 shows an example method for cell configuration associated with asecond part of a base station.

FIG. 24 shows another example method for cell configuration associatedwith a second part of a base station.

FIG. 25 shows an example method for cell configuration associated with awireless device.

FIG. 26 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

The features described herein may enable operation of carrieraggregation and may be used in the technical field of multicarriercommunication systems. Examples may relate cell configuration inmulticarrier communication systems.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description:

-   3GPP 3rd Generation Partnership Project-   5G 5th generation wireless systems-   5GC 5G Core Network-   ACK Acknowledgement-   AMF Access and Mobility Management Function-   ASIC application-specific integrated circuit-   BPSK binary phase shift keying-   CA carrier aggregation-   CC component carrier-   CDMA code division multiple access-   CP cyclic prefix-   CPLD complex programmable logic devices-   CSI channel state information-   CSS common search space-   CU central unit-   DC dual connectivity-   DFTS-OFDM discrete Fourier transform spreading OFDM-   DL downlink-   DU distributed unit-   eLTE enhanced LTE-   eNB evolved Node B-   EPC evolved packet core-   E-UTRAN evolved-universal terrestrial radio access network-   FDD frequency division multiplexing-   FPGA field programmable gate arrays-   Fs-C Fs-control plane-   Fs-U Fs-user plane-   gNB next generation node B-   HARQ hybrid automatic repeat request-   HDL hardware description languages-   ID identifier-   IE information element-   LTE long term evolution-   MAC media access control-   MCG master cell group-   MIB master information block-   MME mobility management entity-   NACK Negative Acknowledgement-   NAS non-access stratum-   NG CP next generation control plane core-   NGC next generation core-   NG-C NG-control plane-   NG-U NG-user plane-   NR MAC new radio MAC-   NR PDCP new radio PDCP-   NR PHY new radio physical-   NR RLC new radio RLC-   NR RRC new radio RRC-   NR new radio-   NSSAI network slice selection assistance information-   OFDM orthogonal frequency division multiplexing-   PCC primary component carrier-   PCell primary cell-   PDCCH physical downlink control channel-   PDCP packet data convergence protocol-   PDU packet data unit-   PHY physical-   PLMN public land mobile network-   PSCell primary secondary cell-   pTAG primary timing advance group-   PUCCH physical uplink control channel-   QAM quadrature amplitude modulation-   QPSK quadrature phase shift keying-   RA random access-   RACH random access channel-   RAN radio access network-   RAP random access preamble-   RAR random access response-   RB resource blocks-   RLC radio link control-   RRC radio resource control-   RRM radio resource management-   SCC secondary component carrier-   SCell secondary cell-   SCG secondary cell group-   SC-OFDM single carrier-OFDM-   SFN system frame number-   S-GW serving gateway-   SRB signaling radio bearer-   sTAG(s) secondary timing advance group(s)-   TA timing advance-   TAG timing advance group-   TAI tracking area identifier-   TDD time division duplexing-   TDMA time division multiple access-   UE user equipment-   UL uplink-   UPGW user plane gateway-   URLLC ultra-reliable low-latency communications-   VHDL VHSIC hardware description language-   Xn-C Xn-control plane-   Xn-U Xn-user plane-   Xx-C Xx-control plane-   Xx-U Xx-user plane

Examples may be implemented using various physical layer modulation andtransmission mechanisms. Example transmission mechanisms may include,but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/orthe like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may be usedfor signal transmission in the physical layer. Examples of modulationschemes include, but are not limited to: phase, amplitude, code, acombination of these, and/or the like. An example radio transmissionmethod may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM,and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example,arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDMsystem. The OFDM system may use technology such as OFDM technology,DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 showsa subcarrier transmitting information symbols. FIG. 1 is shown as anexample, and a typical multicarrier OFDM system may include moresubcarriers in a carrier. For example, the number of subcarriers in acarrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 showstwo guard bands 106 and 107 in a transmission band. As shown in FIG. 1,guard band 106 is between subcarriers 103 and subcarriers 104. Theexample set of subcarriers A 102 includes subcarriers 103 andsubcarriers 104. FIG. 1 also shows an example set of subcarriers B 105.As shown, there is no guard band between any two subcarriers in theexample set of subcarriers B 105. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 2 shows an example timing arrangement with transmission time andreception time for two carriers. A multicarrier OFDM communicationsystem may include one or more carriers, for example, ranging from 1 to10 carriers. Carrier A 204 and carrier B 205 may have the same ordifferent timing structures. Although FIG. 2 shows two synchronizedcarriers, carrier A 204 and carrier B 205 may or may not be synchronizedwith each other. Different radio frame structures may be supported forFDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing.Downlink and uplink transmissions may be organized into radio frames201. In this example, radio frame duration is 10 milliseconds (msec).Other frame durations, for example, in the range of 1 to 100 msec mayalso be supported. Each 10 msec radio frame 201 may be divided into tenequally sized subframes 202. Other subframe durations such as including0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s)may comprise two or more slots (e.g., slots 206 and 207). For theexample of FDD, 10 subframes may be available for downlink transmissionand 10 subframes may be available for uplink transmissions in each 10msec interval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may include all downlink, all uplink, or a downlink part andan uplink part, and/or alike. Slot aggregation may be supported, forexample, data transmission may be scheduled to span one or multipleslots. For example, a mini-slot may start at an OFDM symbol in asubframe. A mini-slot may have a duration of one or more OFDM symbols.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 shows an example of OFDM radio resources. The resource gridstructure in time 304 and frequency 305 is shown in FIG. 3. The quantityof downlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g., 301).Resource elements may be grouped into resource blocks (e.g., 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g., 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. A resource block may correspond to one slot in the timedomain and 180 kHz in the frequency domain (for 15 kHz subcarrierbandwidth and 12 subcarriers).

Multiple numerologies may be supported. A numerology may be derived byscaling a basic subcarrier spacing by an integer N. Scalable numerologymay allow at least from 15 kHz to 480 kHz subcarrier spacing. Thenumerology with 15 kHz and scaled numerology with different subcarrierspacing with the same CP overhead may align at a symbol boundary every 1msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wirelessdevice 406. A communication network 400 may include at least one basestation 401 and at least one wireless device 406. The base station 401may include at least one communication interface 402, one or moreprocessors 403, and at least one set of program code instructions 405stored in non-transitory memory 404 and executable by the one or moreprocessors 403. The wireless device 406 may include at least onecommunication interface 407, one or more processors 408, and at leastone set of program code instructions 410 stored in non-transitory memory409 and executable by the one or more processors 408. A communicationinterface 402 in the base station 401 may be configured to engage incommunication with a communication interface 407 in the wireless device406, such as via a communication path that includes at least onewireless link 411. The wireless link 411 may be a bi-directional link.The communication interface 407 in the wireless device 406 may also beconfigured to engage in communication with the communication interface402 in the base station 401. The base station 401 and the wirelessdevice 406 may be configured to send and receive data over the wirelesslink 411 using multiple frequency carriers. Base stations, wirelessdevices, and other communication devices may include structure andoperations of transceiver(s). Transceivers, which may comprise both atransmitter and receiver, may be employed in devices such as wirelessdevices, base stations, relay nodes, and/or the like. Examples for radiotechnology implemented in the communication interfaces 402, 407 and thewireless link 411 are shown in FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text. The communication network 400 may comprise any numberand/or type of devices, such as, for example, computing devices,wireless devices, mobile devices, handsets, tablets, laptops, internetof things (IoT) devices, hotspots, cellular repeaters, computingdevices, and/or, more generally, user equipment (e.g., UE). Although oneor more of the above types of devices may be referenced herein (e.g.,UE, wireless device, computing device, etc.), it should be understoodthat any device herein may comprise any one or more of the above typesof devices or similar devices. The communication network 400, and anyother network referenced herein, may comprise an LTE network, a 5Gnetwork, or any other network for wireless communications. Apparatuses,systems, and/or methods described herein may generally be described asimplemented on one or more devices (e.g., wireless device, base station,eNB, gNB, computing device, etc.), in one or more networks, but it willbe understood that one or more features and steps may be implemented onany device and/or in any network. As used throughout, the term “basestation” may comprise one or more of: a base station, a node, a Node B,a gNB, an eNB, an ng-eNB, a relay node (e.g., an integrated access andbackhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB,etc.), an access point (e.g., a Wi-Fi access point), a computing device,a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. As used throughout, theterm “wireless device” may comprise one or more of: a UE, a handset, amobile device, a computing device, a node, a device capable ofwirelessly communicating, or any other device capable of sending and/orreceiving signals. Any reference to one or more of these terms/devicesalso considers use of any other term/device mentioned above.

The communications network 400 may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 401) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 406). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. Base station 401 may comprise one or moreof a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, for example, packet filtering,gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink trafficverification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3^(rd) GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or a non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ora non-operational state. The hardware, software, firmware, registers,memory values, and/or the like may be “configured” within a device,whether the device is in an operational or a nonoperational state, toprovide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or a non-operationalstate.

A network (e.g., a 5G network) may include a multitude of base stations,providing a user plane NR PDCP/NR RLC/NR MAC/NR PHY and control plane(e.g., NR RRC) protocol terminations towards the wireless device. Thebase station(s) may be interconnected with other base station(s) (e.g.,employing an Xn interface). The base stations may also be connectedemploying, for example, an NG interface to an NGC. FIG. 10A and FIG. 10Bshow examples for interfaces between a 5G core network (e.g., NGC) andbase stations (e.g., gNB and eLTE eNB). For example, the base stationsmay be interconnected to the NGC control plane (e.g., NG CP) employingthe NG-C interface and to the NGC user plane (e.g., UPGW) employing theNG-U interface. The NG interface may support a many-to-many relationbetween 5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g., TAI), and atRRC connection re-establishment/handover, one serving cell may providethe security input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC); in the uplink, thecarrier corresponding to the PCell may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC); in the uplink,the carrier corresponding to an SCell may be an Uplink SecondaryComponent Carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context in which it is used). The cell ID may beequally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, reference to a firstphysical cell ID for a first downlink carrier may indicate that thefirst physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.Reference to a first carrier that is activated may equally mean that thecell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining anyof the example features described herein. The disclosed mechanisms maybe performed if certain criteria are met, for example, in a wirelessdevice, a base station, a radio environment, a network, a combination ofthe above, and/or the like. Example criteria may be based, at least inpart, on for example, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like. Ifthe one or more criteria are met, various example embodiments may besatisfied. Therefore, it may be possible to implement examples thatselectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices.Wireless devices may support multiple technologies, and/or multiplereleases of the same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. Referenceto a base station communicating with a plurality of wireless devices mayindicate that a base station may communicate with a subset of the totalwireless devices in a coverage area. A plurality of wireless devices ofa given LTE or 5G release, with a given capability and in a given sectorof the base station, may be used. The plurality of wireless devices mayrefer to a selected plurality of wireless devices, and/or a subset oftotal wireless devices in a coverage area which perform according todisclosed methods, and/or the like. There may be a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices perform based onolder releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or moremessages (e.g. RRC messages) that may comprise a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). The other SImay be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signaling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may send its radio access capability information whichmay be static. A base station may request what capabilities for awireless device to report based on band information. If allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with anetwork. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. If adding a new SCell, dedicatedRRC signaling may be employed to send all required system information ofthe SCell. In connected mode, wireless devices may not need to acquirebroadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRCconnection, (e.g. to establish, modify and/or release RBs, to performhandover, to setup, modify, and/or release measurements, to add, modify,and/or release SCells and cell groups). As part of the RRC connectionreconfiguration procedure, NAS dedicated information may be transferredfrom the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be used to establish (or reestablish, resume) an RRC connection. AnRRC connection establishment procedure may comprise SRB1 establishment.The RRC connection establishment procedure may be used to transfer theinitial NAS dedicated information message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure, for example, after successful securityactivation. A measurement report message may be employed to transmitmeasurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture foruplink and downlink signal transmission. FIG. 5A shows an example for anuplink physical channel. The baseband signal representing the physicaluplink shared channel may perform the following processes, which may beperformed by the structures described below. These structures andcorresponding functions are shown as examples, and it is anticipatedthat other mechanisms may be implemented in various examples. Thestructures and corresponding functions may comprise, for example, one ormore scrambling devices 501A and 501B configured to perform scramblingof coded bits in each of the codewords to be transmitted on a physicalchannel; one or more modulation mappers 502A and 502B configured toperform modulation of scrambled bits to generate complex-valued symbols;a layer mapper 503 configured to perform mapping of the complex-valuedmodulation symbols onto one or several transmission layers; one or moretransform precoders 504A and 504B to generate complex-valued symbols; aprecoding device 505 configured to perform precoding of thecomplex-valued symbols; one or more resource element mappers 506A and506B configured to perform mapping of precoded complex-valued symbols toresource elements; one or more signal generators 507A and 507Bconfigured to perform the generation of a complex-valued time-domainDFTS-OFDM/SC-FDMA signal for each antenna port; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion tothe carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA basebandsignal, for example, for each antenna port and/or for the complex-valuedphysical random access channel (PRACH) baseband signal. For example, thebaseband signal, represented as s₁(t), may be split, by a signalsplitter 510, into real and imaginary components, Re{s₁(t)} and Im{s₁},respectively. The real component may be modulated by a modulator 511A,and the imaginary component may be modulated by a modulator 511B. Theoutput signal of the modulator 511A and the output signal of themodulator 511B may be mixed by a mixer 512. The output signal of themixer 512 may be input to a filtering device 513, and filtering may beemployed by the filtering device 513 prior to transmission.

FIG. 5C shows an example structure for downlink transmissions. Thebaseband signal representing a downlink physical channel may perform thefollowing processes, which may be performed by structures describedbelow. These structures and corresponding functions are shown asexamples, and it is anticipated that other mechanisms may be implementedin various examples. The structures and corresponding functions maycomprise, for example, one or more scrambling devices 531A and 531Bconfigured to perform scrambling of coded bits in each of the codewordsto be transmitted on a physical channel; one or more modulation mappers532A and 532B configured to perform modulation of scrambled bits togenerate complex-valued modulation symbols; a layer mapper 533configured to perform mapping of the complex-valued modulation symbolsonto one or several transmission layers; a precoding device 534configured to perform precoding of the complex-valued modulation symbolson each layer for transmission on the antenna ports; one or moreresource element mappers 535A and 535B configured to perform mapping ofcomplex-valued modulation symbols for each antenna port to resourceelements; one or more OFDM signal generators 536A and 536B configured toperform the generation of complex-valued time-domain OFDM signal foreach antenna port; and/or the like.

FIG. 5D shows an example structure for modulation and up-conversion tothe carrier frequency of the complex-valued OFDM baseband signal foreach antenna port. For example, the baseband signal, represented as s₁^((p))(t), may be split, by a signal splitter 520, into real andimaginary components, Re{s₁ ^((p))(t)} and Im{s₁ ^((p))(t)},respectively. The real component may be modulated by a modulator 521A,and the imaginary component may be modulated by a modulator 521B. Theoutput signal of the modulator 521A and the output signal of themodulator 521B may be mixed by a mixer 522. The output signal of themixer 522 may be input to a filtering device 523, and filtering may beemployed by the filtering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA andmulti-connectivity. NR may support multi-connectivity operation, wherebya multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTEDmay be configured to utilize radio resources provided by multipleschedulers located in multiple gNBs connected via a non-ideal or idealbackhaul over the Xn interface. gNBs involved in multi-connectivity fora certain wireless device may assume two different roles: a gNB mayeither act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610or 620). In multi-connectivity, a wireless device may be connected toone master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610and/or 620). Any one or more of the Master gNB 600 and/or the secondarygNBs 610 and 620 may be a Next Generation (NG) NodeB. The master gNB 600may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NR PDCP604 and 605. The secondary gNB may comprise protocol layers NR MAC 611,NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may compriseprotocol layers NR MAC 621, NR RLC 622 and 623, and NR PDCP 624. Themaster gNB 600 may communicate via an interface 606 and/or via aninterface 607, the secondary gNB 610 may communicate via an interface615, and the secondary gNB 620 may communicate via an interface 625. Themaster gNB 600 may also communicate with the secondary gNB 610 and thesecondary gNB 621 via interfaces 608 and 609, respectively, which mayinclude Xn interfaces. For example, the master gNB 600 may communicatevia the interface 608, at layer NR PDCP 605, and with the secondary gNB610 at layer NR RLC 612. The master gNB 600 may communicate via theinterface 609, at layer NR PDCP 605, and with the secondary gNB 620 atlayer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, forexample, if a Master Cell Group (MCG) and a Secondary Cell Group (SCG)are configured. Media Broadcast Multicast Service (MBMS) reception maybe included but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is set up. As an example, threealternatives may exist, an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 6. NR RRC may be located in a master gNBand SRBs may be configured as an MCG bearer type and may use the radioresources of the master gNB. Multi-connectivity may have at least onebearer configured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured withmultiple NR MAC entities: e.g., one NR MAC entity for a master gNB, andother NR MAC entities for secondary gNBs. In multi-connectivity, theconfigured set of serving cells for a wireless device may comprise twosubsets: e.g., the Master Cell Group (MCG) including the serving cellsof the master gNB, and the Secondary Cell Groups (SCGs) including theserving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier(CC) and one of the UL CCs, for example, named PSCell (or PCell of SCG,or sometimes called PCell), may be configured with PUCCH resources. Ifthe SCG is configured, there may be at least one SCG bearer or one splitbearer. If a physical layer problem or a random access problem on aPSCell occurs or is detected, if the maximum number of NR RLCretransmissions has been reached associated with the SCG, or if anaccess problem on a PSCell during a SCG addition or a SCG change occursor is detected, then an RRC connection re-establishment procedure maynot be triggered, UL transmissions towards cells of the SCG may bestopped, a master gNB may be informed by the wireless device of a SCGfailure type, and for a split bearer the DL data transfer over themaster gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearermay be configured for the split bearer. Like the PCell, a PSCell may notbe de-activated. The PSCell may be changed with an SCG change (e.g.,with a security key change and a RACH procedure). A direct bearer typemay change between a split bearer and an SCG bearer, or a simultaneousconfiguration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may interact for multi-connectivity. Themaster gNB may maintain the RRM measurement configuration of thewireless device, and the master gNB may, (e.g., based on receivedmeasurement reports, and/or based on traffic conditions and/or bearertypes), decide to ask a secondary gNB to provide additional resources(e.g., serving cells) for a wireless device. If a request from themaster gNB is received, a secondary gNB may create a container that mayresult in the configuration of additional serving cells for the wirelessdevice (or the secondary gNB decide that it has no resource available todo so). For wireless device capability coordination, the master gNB mayprovide some or all of the Active Set (AS) configuration and thewireless device capabilities to the secondary gNB. The master gNB andthe secondary gNB may exchange information about a wireless deviceconfiguration, such as by employing NR RRC containers (e.g., inter-nodemessages) carried in Xn messages. The secondary gNB may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary gNB). The secondary gNB may decide which cell is the PSCellwithin the SCG. The master gNB may or may not change the content of theNR RRC configuration provided by the secondary gNB. In an SCG additionand an SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s). Both a master gNB and asecondary gNBs may know the system frame number (SFN) and subframeoffset of each other by operations, administration, and maintenance(OAM) (e.g., for the purpose of discontinuous reception (DRX) alignmentand identification of a measurement gap). If adding a new SCG SCell,dedicated NR RRC signaling may be used for sending required systeminformation of the cell for CA, except, for example, for the SFNacquired from an MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entitiesat a wireless device side. A first MAC entity may comprise a lower layerof an MCG 700, an upper layer of an MCG 718, and one or moreintermediate layers of an MCG 719. The lower layer of the MCG 700 maycomprise, for example, a paging channel (PCH) 701, a broadcast channel(BCH) 702, a downlink shared channel (DL-SCH) 703, an uplink sharedchannel (UL-SCH) 704, and a random access channel (RACH) 705. The one ormore intermediate layers of the MCG 719 may comprise, for example, oneor more hybrid automatic repeat request (HARQ) processes 706, one ormore random access control processes 707, multiplexing and/orde-multiplexing processes 709, logical channel prioritization on theuplink processes 710, and a control processes 708 providing control forthe above processes in the one or more intermediate layers of the MCG719. The upper layer of the MCG 718 may comprise, for example, a pagingcontrol channel (PCCH) 711, a broadcast control channel (BCCH) 712, acommon control channel (CCCH) 713, a dedicated control channel (DCCH)714, a dedicated traffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upperlayer of an SCG 738, and one or more intermediate layers of an SCG 739.The lower layer of the SCG 720 may comprise, for example, a BCH 722, aDL-SCH 723, an UL-SCH 724, and a RACH 725. The one or more intermediatelayers of the SCG 739 may comprise, for example, one or more HARQprocesses 726, one or more random access control processes 727,multiplexing and/or de-multiplexing processes 729, logical channelprioritization on the uplink processes 730, and a control processes 728providing control for the above processes in the one or moreintermediate layers of the SCG 739. The upper layer of the SCG 738 maycomprise, for example, a BCCH 732, a DCCH 714, a DTCH 735, and a MACcontrol 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in oneTAG may use the same timing reference. For a given TAG, a wirelessdevice may use at least one downlink carrier as a timing reference. Fora given TAG, a wireless device may synchronize uplink subframe and frametransmission timing of uplink carriers belonging to the same TAG.Serving cells having an uplink to which the same TA applies maycorrespond to serving cells hosted by the same receiver. A wirelessdevice supporting multiple TAs may support two or more TA groups. One TAgroup may include the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not include thePCell and may be called a secondary TAG (sTAG). Carriers within the sameTA group may use the same TA value and/or the same timing reference. IfDC is configured, cells belonging to a cell group (e.g., MCG or SCG) maybe grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprisesa PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprisesa PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. InExample 3, a pTAG comprises a PCell and an SCell1, and an sTAG1comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Upto four TAGs may be supported in a cell group (MCG or SCG), and otherexample TAG configurations may also be provided. In various examples,structures and operations are described for use with a pTAG and an sTAG.Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activatedSCell. The PDCCH order may be sent on a scheduling cell of this SCell.If cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention-based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 shows an example of random access processes, and a correspondingmessage flow, in a secondary TAG. A base station, such as an eNB, maytransmit an activation command 900 to a wireless device, such as a UE.The activation command 900 may be transmitted to activate an SCell. Thebase station may also transmit a PDDCH order 901 to the wireless device,which may be transmitted, for example, after the activation command 900.The wireless device may begin to perform a RACH process for the SCell,which may be initiated, for example, after receiving the PDDCH order901. A wireless device may transmit to the base station (e.g., as partof a RACH process) a preamble 902 (e.g., Msg1), such as a random accesspreamble (RAP). The preamble 902 may be transmitted after or in responseto the PDCCH order 901. The wireless device may transmit the preamble902 via an SCell belonging to an sTAG. Preamble transmission for SCellsmay be controlled by a network using PDCCH format 1A. The base stationmay send a random access response (RAR) 903 (e.g., Msg2 message) to thewireless device. The RAR 903 may be after or in response to the preamble902 transmission via the SCell. The RAR 903 may be addressed to a randomaccess radio network temporary identifier (RA-RNTI) in a PCell commonsearch space (CSS). If the wireless device receives the RAR 903, theRACH process may conclude. The RACH process may conclude, for example,after or in response to the wireless device receiving the RAR 903 fromthe base station. After the RACH process, the wireless device maytransmit an uplink transmission 904. The uplink transmission 904 maycomprise uplink packets transmitted via the same SCell used for thepreamble 902 transmission.

Timing alignment (e.g., initial timing alignment) for communicationsbetween the wireless device and the base station may be performedthrough a random access procedure, such as described above regardingFIG. 9. The random access procedure may involve a wireless device, suchas a UE, transmitting a random access preamble and a base station, suchas an eNB, responding with an initial TA command NTA (amount of timingadvance) within a random access response window. The start of the randomaccess preamble may be aligned with the start of a corresponding uplinksubframe at the wireless device assuming NTA=0. The eNB may estimate theuplink timing from the random access preamble transmitted by thewireless device. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The wireless device may determine the initial uplinktransmission timing relative to the corresponding downlink of the sTAGon which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. If an eNB performs anSCell addition configuration, the related TAG configuration may beconfigured for the SCell. An eNB may modify the TAG configuration of anSCell by removing (e.g., releasing) the SCell and adding (e.g.,configuring) a new SCell (with the same physical cell ID and frequency)with an updated TAG ID. The new SCell with the updated TAG ID mayinitially be inactive subsequent to being assigned the updated TAG ID.The eNB may activate the updated new SCell and start scheduling packetson the activated SCell. In some examples, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, such as at least one RRC reconfiguration message,may be sent to the wireless device. The at least one RRC message may besent to the wireless device to reconfigure TAG configurations, forexample, by releasing the SCell and configuring the SCell as a part ofthe pTAG. If, for example, an SCell is added or configured without a TAGindex, the SCell may be explicitly assigned to the pTAG. The PCell maynot change its TA group and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify and/or releaseRBs, to perform handover, to setup, modify, and/or release measurements,to add, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the wirelessdevice may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the wirelessdevice may perform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is onlytransmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 andearlier, a wireless device may transmit PUCCH information on one cell(e.g., a PCell or a PSCell) to a given eNB. As the number of CA capablewireless devices increases, and as the number of aggregated carriersincreases, the number of PUCCHs and the PUCCH payload size may increase.Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be used to offload thePUCCH resource from the PCell. More than one PUCCH may be configured.For example, a PUCCH on a PCell may be configured and another PUCCH onan SCell may be configured. One, two, or more cells may be configuredwith PUCCH resources for transmitting CSI, acknowledgment (ACK), and/ornon-acknowledgment (NACK) to a base station. Cells may be grouped intomultiple PUCCH groups, and one or more cells within a group may beconfigured with a PUCCH. One SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

A MAC entity may have a configurable timer, for example,timeAlignmentTimer, per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the serving cells belonging tothe associated TAG to be uplink time aligned. If a Timing AdvanceCommand MAC control element is received, the MAC entity may apply theTiming Advance Command for the indicated TAG; and/or the MAC entity maystart or restart the timeAlignmentTimer associated with a TAG that maybe indicated by the Timing Advance Command MAC control element. If aTiming Advance Command is received in a Random Access Response messagefor a serving cell belonging to a TAG, the MAC entity may apply theTiming Advance Command for this TAG and/or start or restart thetimeAlignmentTimer associated with this TAG. Additionally oralternatively, if the Random Access Preamble is not selected by the MACentity, the MAC entity may apply the Timing Advance Command for this TAGand/or start or restart the timeAlignmentTimer associated with this TAG.If the timeAlignmentTimer associated with this TAG is not running, theTiming Advance Command for this TAG may be applied, and thetimeAlignmentTimer associated with this TAG may be started. If thecontention resolution is not successful, a timeAlignmentTimer associatedwith this TAG may be stopped. If the contention resolution issuccessful, the MAC entity may ignore the received Timing AdvanceCommand The MAC entity may determine whether the contention resolutionis successful or whether the contention resolution is not successful.

A timer may be considered to be running after it is started, until it isstopped, or until it expires; otherwise it may be considered to not berunning A timer can be started if it is not running or restarted if itis running. For example, a timer may be started or restarted from itsinitial value.

Features described herein may enable operation of multi-carriercommunications. Features may comprise a non-transitory tangible computerreadable media comprising instructions executable by one or moreprocessors to cause operation of multi-carrier communications. Thefeatures may comprise an article of manufacture that comprises anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a device (e.g. wireless communicator, UE, base station, etc.)to enable operation of multi-carrier communications. The devices hereinmay include processors, memory, interfaces, and/or the like. Featuresmay comprise communication networks comprising devices such as basestations, wireless devices (or user equipment: UE), servers, switches,antennas, and/or the like.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A basestation, such as a gNB 1020, may be interconnected to an NGC 1010control plane employing an NG-C interface. The base station, forexample, the gNB 1020, may also be interconnected to an NGC 1010 userplane (e.g., UPGW) employing an NG-U interface. As another example, abase station, such as an eLTE eNB 1040, may be interconnected to an NGC1030 control plane employing an NG-C interface. The base station, forexample, the eLTE eNB 1040, may also be interconnected to an NGC 1030user plane (e.g., UPGW) employing an NG-U interface. An NG interface maysupport a many-to-many relation between 5G core networks and basestations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexamples for architectures of tight interworking between a 5G RAN and anLTE RAN. The tight interworking may enable a multiplereceiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED stateto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g., an eLTE eNB and a gNB). The two basestations may be connected via a non-ideal or ideal backhaul over the Xxinterface between an LTE eNB and a gNB, or over the Xn interface betweenan eLTE eNB and a gNB. Base stations involved in tight interworking fora certain wireless device may assume different roles. For example, abase station may act as a master base station or a base station may actas a secondary base station. In tight interworking, a wireless devicemay be connected to both a master base station and a secondary basestation. Mechanisms implemented in tight interworking may be extended tocover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, whichmay be connected to EPC nodes 1101A or 1101B, respectively. Thisconnection to EPC nodes may be, for example, to an MME via the S1-Cinterface and/or to an S-GW via the S1-U interface. A secondary basestation may be a gNB 1103A or a gNB 1103B, either or both of which maybe a non-standalone node having a control plane connection via an Xx-Cinterface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B).In the tight interworking architecture of FIG. 11A, a user plane for agNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-Uinterface between the LTE eNB and the gNB, and via an S1-U interfacebetween the LTE eNB and the S-GW. In the architecture of FIG. 11B, auser plane for a gNB (e.g., the gNB 1103B) may be connected directly toan S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB andthe S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may beconnected to NGC nodes 1101C or 1101D, respectively. This connection toNGC nodes may be, for example, to a control plane core node via the NG-Cinterface and/or to a user plane core node via the NG-U interface. Asecondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C orthe gNB 1103D). In the tight interworking architecture of FIG. 11C, auser plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connectedto a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., thegNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, andvia an NG-U interface between the gNB and the user plane core node. Inthe architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., theeLTE eNB 1102D) may be connected directly to a user plane core node(e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and theuser plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F,which may be connected to NGC nodes 1101E or 1101F, respectively. Thisconnection to NGC nodes may be, for example, to a control plane corenode via the NG-C interface and/or to a user plane core node via theNG-U interface. A secondary base station may be a gNB 1103E or a gNB1103F, either or both of which may be a non-standalone node having acontrol plane connection via an Xn-C interface to an eLTE eNB (e.g., theeLTE eNB 1102E or the eLTE eNB 1102F). In the tight interworkingarchitecture of FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E)may be connected to a user plane core node (e.g., the NGC 1101E) throughan eLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface betweenthe eLTE eNB and the gNB, and via an NG-U interface between the eLTE eNBand the user plane core node. In the architecture of FIG. 11F, a userplane for a gNB (e.g., the gNB 1103F) may be connected directly to auser plane core node (e.g., the NGC 1101F) via an NG-U interface betweenthe gNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocolstructures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A maybe an S1 secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The LTE eNB1201A may be connected to an EPC with a non-standalone gNB 1210A, via anXx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A,and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with thePDCP 1205A, and a split bearer type may interface with the PDCP 1206A.The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A andNR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface withthe NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The gNB1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B,via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type mayinterface with the NR PDCP 1205B, and a split bearer type may interfacewith the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layersMAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer typemay interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The eLTE eNB1201C may be connected to an NGC with a non-standalone gNB 1210C, via anXn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C,and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with thePDCP 1205C, and a split bearer type may interface with the PDCP 1206C.The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C andNR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface withthe NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. At least threealternatives may exist, for example, an MCG bearer, an SCG bearer, and asplit bearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NRRRC may be located in a master base station, and the SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may have at least one bearerconfigured to use radio resources provided by the secondary basestation. Tight interworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., oneMAC entity for a master base station, and one MAC entity for a secondarybase station. In tight interworking, the configured set of serving cellsfor a wireless device may comprise of two subsets: e.g., the Master CellGroup (MCG) including the serving cells of the master base station, andthe Secondary Cell Group (SCG) including the serving cells of thesecondary base station.

At least one cell in a SCG may have a configured UL CC and one of them,for example, a PSCell (or the PCell of the SCG, which may also be calleda PCell), is configured with PUCCH resources. If the SCG is configured,there may be at least one SCG bearer or one split bearer. If one or moreof a physical layer problem or a random access problem is detected on aPSCell, if the maximum number of (NR) RLC retransmissions associatedwith the SCG has been reached, and/or if an access problem on a PSCellduring an SCG addition or during an SCG change is detected, then: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG may be stopped, a master basestation may be informed by the wireless device of a SCG failure type,and/or for a split bearer the DL data transfer over the master basestation may be maintained. The RLC AM bearer may be configured for thesplit bearer. Like the PCell, a PSCell may not be de-activated. A PSCellmay be changed with an SCG change, for example, with security key changeand a RACH procedure. A direct bearer type change, between a splitbearer and an SCG bearer, may not be supported. Simultaneousconfiguration of an SCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. Themaster base station may maintain the RRM measurement configuration ofthe wireless device. The master base station may determine to ask asecondary base station to provide additional resources (e.g., servingcells) for a wireless device. This determination may be based on, forexample, received measurement reports, traffic conditions, and/or bearertypes. If a request from the master base station is received, asecondary base station may create a container that may result in theconfiguration of additional serving cells for the wireless device, orthe secondary base station may determine that it has no resourceavailable to do so. The master base station may provide at least part ofthe AS configuration and the wireless device capabilities to thesecondary base station, for example, for wireless device capabilitycoordination. The master base station and the secondary base station mayexchange information about a wireless device configuration such as byusing RRC containers (e.g., inter-node messages) carried in Xn or Xxmessages. The secondary base station may initiate a reconfiguration ofits existing serving cells (e.g., PUCCH towards the secondary basestation). The secondary base station may determine which cell is thePSCell within the SCG. The master base station may not change thecontent of the RRC configuration provided by the secondary base station.If an SCG is added and/or an SCG SCell is added, the master base stationmay provide the latest measurement results for the SCG cell(s). Eitheror both of a master base station and a secondary base station may knowthe SFN and subframe offset of each other by OAM, (e.g., for the purposeof DRX alignment and identification of a measurement gap). If a new SCGSCell is added, dedicated RRC signaling may be used for sending requiredsystem information of the cell, such as for CA, except, for example, forthe SFN acquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 anda core 1310 may interface with other nodes via RAN-CN interfaces. In anon-centralized deployment example, the full protocol stack (e.g., NRRRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node,such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304.These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTEeNB 1304) may interface with one of more of each other via a respectiveinter-BS interface. In a centralized deployment example, upper layers ofa gNB may be located in a Central Unit (CU) 1311, and lower layers ofthe gNB may be located in Distributed Units (DU) 1312, 1313, and 1314.The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide acontrol plane connection over the Fs interface, and the Fs-U may providea user plane connection over the Fs interface. In the centralizeddeployment, different functional split options between the CU 1311 andthe DUs 1312, 1313, and 1314 may be possible by locating differentprotocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312,1313, and 1314. The functional split may support flexibility to move theRAN functions between the CU 1311 and the DUs 1312, 1313, and 1314depending on service requirements and/or network environments. Thefunctional split option may change during operation (e.g., after the Fsinterface setup procedure), or the functional split option may changeonly in the Fs setup procedure (e.g., the functional split option may bestatic during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of acentralized gNB deployment. Element numerals that are followed by “A” or“B” designations in FIG. 14 may represent the same elements in differenttraffic flows, for example, either receiving data (e.g., data 1402A) orsending data (e.g., 1402B). In the split option example 1, an NR RRC1401 may be in a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising aHigh NR RLC 1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprisinga High NR MAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g.,comprising a High NR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410may be in a DU. In the split option example 2, the NR RRC 1401 and theNR PDCP 1403 may be in a CU, and the NR RLC, the NR MAC, the NR PHY, andthe RF 1410 may be in a DU. In the split option example 3, the NR RRC1401, the NR PDCP 1403, and a partial function of the NR RLC (e.g., theHigh NR RLC 1404) may be in a CU, and the other partial function of theNR RLC (e.g., the Low NR RLC 1405), the NR MAC, the NR PHY, and the RF1410 may be in a DU. In the split option example 4, the NR RRC 1401, theNR PDCP 1403, and the NR RLC may be in a CU, and the NR MAC, the NR PHY,and the RF 1410 may be in a DU. In the split option example 5, the NRRRC 1401, the NR PDCP 1403, the NR RLC, and a partial function of the NRMAC (e.g., the High NR MAC 1406) may be in a CU, and the other partialfunction of the NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and theRF 1410 may be in a DU. In the split option example 6, the NR RRC 1401,the NR PDCP 1403, the NR RLC, and the NR MAC may be in CU, and the NRPHY and the RF 1410 may be in a DU. In the split option example 7, theNR RRC 1401, the NR PDCP 1403, the NR RLC, the NR MAC, and a partialfunction of the NR PHY (e.g., the High NR PHY 1408) may be in a CU, andthe other partial function of the NR PHY (e.g., the Low NR PHY 1409) andthe RF 1410 may be in a DU. In the split option example 8, the NR RRC1401, the NR PDCP 1403, the NR RLC, the NR MAC, and the NR PHY may be ina CU, and the RF 1410 may be in a DU.

The functional split may be configured per CU, per DU, per wirelessdevice, per bearer, per slice, and/or with other granularities. In a perCU split, a CU may have a fixed split, and DUs may be configured tomatch the split option of the CU. In a per DU split, each DU may beconfigured with a different split, and a CU may provide different splitoptions for different DUs. In a per wireless device split, a gNB (e.g.,a CU and a DU) may provide different split options for differentwireless devices. In a per bearer split, different split options may beutilized for different bearer types. In a per slice splice, differentsplit options may be applied for different slices.

A new radio access network (new RAN) may support different networkslices, which may allow differentiated treatment customized to supportdifferent service requirements with end to end scope. The new RAN mayprovide a differentiated handling of traffic for different networkslices that may be pre-configured, and the new RAN may allow a singleRAN node to support multiple slices. The new RAN may support selectionof a RAN part for a given network slice, for example, by one or moreslice ID(s) or NSSAI(s) provided by a wireless device or provided by anNGC (e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one ormore of pre-configured network slices in a PLMN. For an initial attach,a wireless device may provide a slice ID and/or an NSSAI, and a RAN node(e.g., a gNB) may use the slice ID or the NSSAI for routing an initialNAS signaling to an NGC control plane function (e.g., an NG CP). If awireless device does not provide any slice ID or NSSAI, a RAN node maysend a NAS signaling to a default NGC control plane function. Forsubsequent accesses, the wireless device may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. If the RAN resource isolation is implemented, shortageof shared resources in one slice does not cause a break in a servicelevel agreement for another slice.

The amount of data traffic carried over networks is expected to increasefor many years to come. The number of users and/or devices isincreasing, and each user/device accesses an increasing number andvariety of services, for example, video delivery, large files, andimages. This requires not only high capacity in the network, but alsoprovisioning very high data rates to meet customers' expectations oninteractivity and responsiveness. More spectrum may be required fornetwork operators to meet the increasing demand Considering userexpectations of high data rates along with seamless mobility, it isbeneficial that more spectrum be made available for deploying macrocells as well as small cells for communication systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, if present, may be an effectivecomplement to licensed spectrum for network operators, for example, tohelp address the traffic explosion in some examples, such as hotspotareas. Licensed Assisted Access (LAA) offers an alternative foroperators to make use of unlicensed spectrum, for example, if managingone radio network, offering new possibilities for optimizing thenetwork's efficiency.

Listen-before-talk (clear channel assessment) may be implemented fortransmission in an LAA cell. In a listen-before-talk (LBT) procedure,equipment may apply a clear channel assessment (CCA) check before usingthe channel. For example, the CCA may utilize at least energy detectionto determine the presence or absence of other signals on a channel todetermine if a channel is occupied or clear, respectively. For example,European and Japanese regulations mandate the usage of LBT in theunlicensed bands. Apart from regulatory requirements, carrier sensingvia LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled. Some of these functions may besupported by one or more signals to be transmitted from the beginning ofa discontinuous LAA downlink transmission. Channel reservation may beenabled by the transmission of signals, by an LAA node, after gainingchannel access, for example, via a successful LBT operation, so thatother nodes that receive the transmitted signal with energy above acertain threshold sense the channel to be occupied. Functions that mayneed to be supported by one or more signals for LAA operation withdiscontinuous downlink transmission may include one or more of thefollowing: detection of the LAA downlink transmission (including cellidentification) by wireless devices, time synchronization of wirelessdevices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-Acarrier aggregation timing relationships across serving cells aggregatedby CA. This may not indicate that the eNB transmissions may start onlyat the subframe boundary. LAA may support transmitting PDSCH if not allOFDM symbols are available for transmission in a subframe according toLBT. Delivery of necessary control information for the PDSCH may also besupported.

LBT procedures may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, forexample, in Europe, specify an energy detection threshold such that if anode receives energy greater than this threshold, the node assumes thatthe channel is not free. Nodes may follow such regulatory requirements.A node may optionally use a lower threshold for energy detection thanthat specified by regulatory requirements. LAA may employ a mechanism toadaptively change the energy detection threshold, for example, LAA mayemploy a mechanism to adaptively change (e.g., lower or increase) theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. A Category4 LBT mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, insome implementation scenarios, in some situations, and/or in somefrequencies, no LBT procedure may performed by the transmitting entity.Category 2 (e.g., LBT without random back-off) may be implemented. Theduration of time that the channel is sensed to be idle before thetransmitting entity transmits may be deterministic. Category 3 (e.g.,LBT with random back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle, for example, before the transmitting entity transmitson the channel. Category 4 (e.g., LBT with random back-off with acontention window of variable size) may be implemented. The transmittingentity may draw a random number N within a contention window. The sizeof contention window may be specified by the minimum and maximum valueof N. The transmitting entity may vary the size of the contention windowif drawing the random number N. The random number N may be used in theLBT procedure to determine the duration of time that the channel issensed to be idle, for example, before the transmitting entity transmitson the channel

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

LAA may use uplink LBT at the wireless device. The UL LBT scheme may bedifferent from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DLtransmitting node, for example, with no transmission immediately beforeor after from the same node on the same CC. An UL transmission burstfrom a wireless device perspective may be a continuous transmission froma wireless device, for example, with no transmission immediately beforeor after from the same wireless device on the same CC. A UL transmissionburst may be defined from a wireless device perspective or from a basestation perspective. If a base station is operating DL and UL LAA overthe same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. An instant in time may be part of a DLtransmission burst or part of an UL transmission burst.

One or more logical channels of a bearer may be used for sendingoriginal packets and/or duplicated packets, for example, if packet dataconvergence protocol (PDCP) packet duplication is configured for thebearer. Original packets and/or duplicated packets may be sent viavarious cells associated with the logical channels. A first group ofcells may be used for sending original packets. A second group of cellsmay be used for sending duplicated packets. The first group of cells maybe different from the second group of cells. If a particular group ofcells (e.g., the first group of cells or the second group of cells)fails to deliver packets to a destination (e.g., a wireless device indownlink transmission, a base station in uplink transmission, etc.),another group of cells (e.g., the other of the first group of cells orthe second group of cells that has not failed) may still be able todeliver the packets to the destination.

One or more parts of a base station or multiple base stations (e.g., abase station central unit (CU) and/or a base station distributed unit(DU)) may select the cells associated with the logical channels. Forexample, each of the base station CU and the base station DU may haveinformation that may be used for selecting the cells. The base stationCU may have higher layer information (e.g., radio resource control (RRC)information) associated with the cells, load status of the cells,overall channel quality status of the cells, and/or the like. The basestation DU may have lower layer information associated with the cells.

Performance of packet duplication may be decreased, for example, if abase station DU configures cells without knowing information from a basestation CU. Performance of wireless communications may be decreased, forexample, if a base station CU and a base station DU does not have aprocess to share cell configuration (e.g., determination or selection)information for duplicated PDCP packets (e.g., second logical channel)and/or original PDCP packets (e.g., first logical channel) of a bearer.A process to share cell configuration information for duplicated packetsand/or original PDCP packets may comprise, for example, sharing a resultof selecting first cells for a first logical channel of the bearer andselecting second cells for a second logical channel for duplications ofPDCP packets of the first logical channel and/or the bearer.

A base station CU and/or a base station DU, for example, may share itsinformation associated with cell configuration with its counterpart,which may help avoid and/or alleviate the above and/or other issues. Abase station DU may select first cells for a first logical channel(e.g., for original PDCP packets) and second cells for a second logicalchannel (e.g., for duplicated PDCP packets) based on PDCP duplicationinformation. The PDCP duplication information may be received from abase station CU (e.g., Duplication Indication IE, which may be indicatedby a true/false indication). The base station DU may send (e.g.,transmit) the selection information to the base station CU. A basestation CU may select first cells for a first logical channel (e.g., fororiginal PDCP packets) and second cells for a second logical channel(e.g., for duplicated PDCP packets). The base station CU may send (e.g.,transmit) the selection information to the base station DU. Exampleprocesses may be described herein as being performed by a base stationCU and/or a base station DU, but the example processes may additionallyor alternatively be performed by any two parts of a base station ormultiple base stations.

A base station CU (e.g., gNB-CU), for example, may send (e.g.,transmit), to a base station DU (e.g., gNB-DU), PDCP duplicationinformation for a bearer of a wireless device. The base station DUand/or the base station CU may configure a first logical channel and/ora second logical channel for PDCP duplication of the bearer. The secondlogical channel may be used to send (e.g., transmit) duplications ofPDCP packets of the first logical channel (e.g., PDCP duplicationpackets of the bearer). The base station DU may determine one or morefirst cells for the first logical channel and/or one or more secondcells for the second logical channel. The base station DU may send(e.g., transmit), to the base station CU, the determined cellinformation for the first logical channel and for the second logicalchannel. The base station CU may determine one or more first cells forthe first logical channel and one or more second cells for the secondlogical channel. The base station CU may send (e.g., transmit), to thebase station DU, the determined cell information for the first logicalchannel and for the second logical channel. The base station CU mayfurther send the determined cell information to the wireless device viaan RRC message. The base station CU may send (e.g., transmit) the RRCmessage to the wireless device via the base station DU. The base stationDU may not send duplicated PDCP packets (e.g., packets of the secondlogical channel) via cells for original PDCP packets. The second logicalchannel for duplicated PDCP packets may use first cells different fromsecond cells used by the first logical channel for original PDCPpackets.

A base station (e.g., gNB, eNB, and/or the like) may comprise one ormore parts. For example, a base station may comprise a base station CU(e.g., gNB-CU) and one or more base station DUs (e.g., gNB-DU). Exampleprocesses may be described herein as being performed by a base stationCU and/or a base station DU, but the example processes may additionallyor alternatively be performed by any two parts of a base station ormultiple base stations. The base station CU may provide functionalitiesof a PDCP layer and/or an SDAP layer for wireless devices. A basestation DU of the one or more base station DUs may providefunctionalities of an RLC layer, a MAC layer, and/or a PHY layer (e.g.,for wireless devices). The base station CU may implement one or moreupper layers among a PDCP layer, an SDAP layer, an RLC layer, a MAClayer, and/or a PHY layer. The base station DU may implement one or morelower layers among a PDCP layer, an SDAP layer, an RLC layer, a MAClayer, and/or a PHY layer. The base station CU may be connected to,and/or in communication with, the one or more base station DUs , forexample, via one or more F1 interfaces. The base station CU maycommunicate with the base station DU via an F1 interface.

The base station (e.g., the base station CU) may configure a firstbearer for a wireless device. The base station CU may send a firstmessage, such as an F1 message. The first message may comprise one ormore of: a wireless device (e.g., UE) context setup request message, awireless device (e.g., UE) context modification request message, awireless device (e.g., UE) context modification confirm message, and/orthe like. The first message may indicate a request to setup the firstbearer for the wireless device. The first message (e.g., an F1 message)may comprise one or more of: an identifier of the wireless device (e.g.,wireless device identifier such as a UE ID, a gNB-CU UE F1AP ID, agNB-DU UE F1AP ID, etc.); a TMSI, a GUTI, an IMSI, a C-RNTI, and/or thelike; an identifier of the first bearer, a first uplink GTP tunnelendpoint identifier (e.g., UL TEID) of a first uplink GTP tunnel for thefirst bearer, one or more bearer identifiers of one or more bearersrequested to be setup, and/or one or more logical channels of the firstbearer. The first message may comprise RRC information (e.g., CU to DURRC Information). The first message may comprise cell group information(E.g., CG-ConfigInfo). The one or more bearers requested to be setup maycomprise one or more of a signaling radio bearer (SRB) and/or a dataradio bearer (DRB).

The base station DU, for example, may setup the first bearer for thewireless device (e.g., allocate radio resources for the first bearer,setup PHY/MAC/RLC configuration parameters for the first bearer, and/orthe like), for example, after or in response to receiving the firstmessage. The base station DU may send a response message (e.g., an F1response message) to the base station CU, for example, after or inresponse to receiving the first message (e.g., the F1 message). Theresponse message may comprise one or more of a list of bearers setup(e.g., which may comprise the first bearer), a list of bearers failed tobe setup, an identifier of the wireless device, and/or the like.

The base station CU, for example, may determine to initiate PDCPduplication for the first bearer of the wireless device. The firstbearer may comprise an SRB and/or a DRB. The base station CU mayinitiate PDCP duplication for the first bearer, for example, to increasetransmission reliability such as by creating a diversity gain ofmultiple packet transmission paths for packets (e.g., a first path fororiginal packets and a second path for duplicated packets). The firstbearer may be used for ultra reliable low latency (URLLC) and/or otherservices (e.g., high priority services).

An additional RLC entity and/or an additional logical channel may beadded to a radio bearer to handle duplicated PDCP PDUs, for example, ifduplication is configured for the radio bearer by RRC. PDCP duplicationmay comprise sending the same PDCP PDUs at least twice (e.g., a firsttime via the original RLC entity and a second time via the additionalRLC entity). By using two independent transmission paths, packetduplication may increase reliability and/or may reduce latency. PDCPduplication may be beneficial for URLLC and/or other services (e.g.,high priority services). Original PDCP PDUs and corresponding duplicatesmay not be sent via the same carrier. At least two different logicalchannels may use a same MAC entity (e.g., if carrier aggregation (CA) isimplemented) and/or different MAC entities (e.g., if dual connectivity(DC) is implemented). Logical channel mapping restrictions may be usedin MAC, for example, may help avoid the logical channel carrying theoriginal PDCP PDUs and/or the logical channel carrying the correspondingduplicates using the same carrier (e.g., if the two logical channels usethe same MAC entity).

PDCP packet duplication may be activated and/or deactivated for a DRBbased on a MAC control element (MAC CE), for example, if PDCP packetduplication is configured. The logical channel mapping restrictions maybe lifted, for example, if PDCP packet duplication is deactivated (e.g.,in CA). Additionally or alternatively, the wireless device may use theMAC CE commands regardless of their origin (e.g., MCG or SCG), forexample, if DC is implemented.

The base station DU, for example, may receive, from the base station CU,a first message comprising bearer configuration parameters at least forthe first bearer for the wireless device. The first message may comprisean F1 message indicating a request to setup the first bearer. The firstmessage may comprise a message indicating a request to modify the firstbearer, for example, if the first bearer is setup by the base station DUbefore the first message. The first message may comprise one or more of:a wireless device (e.g., UE) context setup request message, a wirelessdevice (e.g., UE) context modification request message, a wirelessdevice (e.g., UE) context modification confirm message, and/or the like.The first message may comprise one or more of an identifier of thewireless device (e.g., UE identifier, gNB-CU UE F1AP ID, gNB-DU UE F1APID, TMSI, GUTI, IMSI, C-RNTI, and/or the like), a first beareridentifier of the first bearer, one or more uplink GTP tunnel endpointidentifiers (e.g., UL TEIDs) of one or more uplink GTP tunnels for thefirst bearer and/or one or more logical channels of the first bearer,one or more bearer identifiers of one or more bearers requested to besetup, one or more bearer identifiers of one or more bearers requestedto be modified, and/or the like. The one or more bearers requested to besetup/modified may comprise one or more of an SRB and/or a DRB. Thebearer configuration parameters may be included in a CU To DU RRCInformation IE, in an SRB Setup List IE, and/or in a DRB Setup List IEof the first message. The CU To DU RRC Information IE may furthercomprise RRC parameters determined by the base station CU for thewireless device and/or provided by the wireless device.

The bearer configuration parameters may comprise one or more of: anidentifier of the wireless device, a first bearer identifier of thefirst bearer, a PDCP duplication information for the first bearer,and/or the like. The PDCP duplication information may comprise one ormore of: a logical channel information element (IE), a PDCP duplicationindication IE, and/or the like. The one or more logical channel IE maycomprise a first logical channel identifier of the first logical channelof the first bearer and/or a second logical channel identifier of thesecond logical channel configured to send duplicates of PDCP packets(e.g., PDCP PDUs) of the first logical channel (and/or the firstbearer). For PDCP duplication of three or more times, the one or morelogical channel IE may comprise three or more logical channelidentifiers. The PDCP duplication indication IE may indicate that PDCPpackets of the first bearer are duplicated (e.g., a true or falseindication). The base station DU, for example, may determine logicalchannel identifiers for the first logical channel and/or the secondlogical channel, for example, if the first logical channel identifierand/or the second logical channel identifier is not indicated in thefirst message.

The first message may comprise a first (e.g., uplink GTP) tunnelendpoint identifier (e.g., first UL TEID) of the first (e.g., uplinkGTP) tunnel for the first logical channel of the first bearer and/or asecond (e.g., uplink GTP) tunnel endpoint identifier (e.g., second ULTEID) of the second (e.g., uplink GTP) tunnel for the second logicalchannel of the first bearer. The second logical channel may comprise alogical channel to send duplicates of PDCP packets (e.g., PDCP PDUs) ofthe first logical channel (and/or the first bearer). The first messagemay further comprise at least one of a first IE indicating that thefirst logical channel is a default logical channel of the first bearerand/or a second IE indicating that the second logical channel is forduplicated PDCP packets of the first bearer (and/or of the first logicalchannel).

The first message (e.g., the bearer configuration parameter) maycomprise cell configuration parameters for the first logical channeland/or for the second logical channel. The first message (e.g., thebearer configuration parameter, and/or the cell configuration parametersfor the first logical channel and/or for the second logical channel) maycomprise at least one first cell identifier (e.g., a global cellidentifier (e.g., NCGI, ECGI, CGI, and/or the like), a physical cellidentifier (e.g., PCI), and/or the like) of at least one first cell usedfor the first logical channel of the first bearer and/or at least onesecond cell identifier (e.g., a global cell identifier (e.g., NCGI,ECGI, CGI, and/or the like), a physical cell identifier (e.g., PCI),and/or the like) of at least one second cell used for a second logicalchannel for duplications of PDCP packets of the first logical channel(and/or of the first bearer). The base station CU, for example, maydetermine (e.g., select and/or configure) the at least one first cellfor the first logical channel and/or the at least one second cell forthe second logical channel. The base station CU may determine the atleast one first cell and/or the at least one second cell, for example,based on: a measurement report received from the wireless device (e.g.,via one or more RRC messages), and/or one or more cell configurationparameters received from the base station DU (e.g., via one or more F1messages).

The measurement report may comprise a reference signal received power(RSRP) and/or a reference signal received quality (RSRQ) of one or morecells of the base station DU. The one or more cell configurationparameters received from the base station DU may comprise at least oneof power configuration parameters, beam configuration parameters,subframe scheduling parameters, control channel configurationparameters, one or more elements of system information blocks (e.g.,system information block type 1 to 21), and/or the like for one or morecells of the base station DU.

The base station CU, for example, may determine (e.g., select and/orconfigure, which may be based on the measurement report of cells) the atleast one first cell and/or the at least one second cell such that thefirst logical channel and the second logical channel have similar cellqualities. The base station CU may determine (e.g., select and/orconfigure, which may be based on the measurement report for cells) theat least one first cell and the at least one second cell such that thefirst logical channel has a better cell quality than the cell quality ofthe second logical channel. The base station CU may select, forduplicated packets, the at least one second cell from among secondarycells of the wireless device and/or among LAA cells. Each of the atleast one second cell may be different from any of the at least onefirst cell.

The base station DU, for example, may determine (e.g., select and/orconfigure, which may be based on the bearer configuration parametersand/or the first message) at least one first cell to be used for thefirst logical channel of the first bearer and/or at least one secondcell to be used for the second logical channel of the first bearer. Thesecond logical channel may be for duplicated PDCP packets of the firstbearer (and/or of the first logical channel). The base station DU maydetermine (e.g., select and/or configure, which may be based on thebearer configuration parameters (comprising the PDCP duplicationinformation) and/or the cell configuration parameters of the firstmessage) the at least one first cell and/or the at least one secondcell, for example, if the first message comprises the cell configurationparameters for the first logical channel and/or for the second logicalchannel. The base station DU may determine (e.g., select and/orconfigure) the at least one first cell and/or the at least one secondcell, such as indicated by the base station CU in the first message(e.g., as indicated by the cell configuration parameters), for example,if the first message comprises the cell configuration parameters for thefirst logical channel and/or for the second logical channel. The basestation DU may determine (e.g., select and/or configure, which may bebased on the bearer configuration parameters (comprising the PDCPduplication information without the cell configuration parameters) ofthe first message) the at least one first cell and/or the at least onesecond cell, for example, if the first message does not comprise thecell configuration parameters for the first logical channel and/or forthe second logical channel.

The base station DU, for example, may determine (e.g., select and/orconfigure) the at least one first cell for the first logical channel andthe at least one second cell for the second logical channel. The basestation DU may determine the at least one first cell and/or the at leastone second cell, for example, based on one or more of: a physical layermeasurement report (e.g., CSI report, sounding reference signal, SRSmeasurement) that may be received from the wireless device (e.g., via anair interface), a RRC layer measurement report that may be received fromthe wireless device (e.g., via the base station CU), and/or one or morecell configuration parameters of the base station DU. The one or moreRRC layer measurement report may comprise a reference signal receivedpower (RSRP) and/or a reference signal received quality (RSRQ) of one ormore cells of the base station DU. The one or more cell configurationparameters of the base station DU may comprise one or more of: a powerconfiguration parameter, a beam configuration parameter, a subframescheduling parameter, a control channel configuration parameter, anelement of system information blocks (e.g., system information blocktype 1 to 21), and/or the like for one or more cells of the base stationDU.

The base station DU, for example, may determine (e.g., select and/orconfigure, which may be based on the physical layer measurement reportand/or the one or more RRC layer measurement report for cells) the atleast one first cell and/or the at least one second cell such that thefirst logical channel and the second logical channel have similar cellqualities. The base station DU may determine (e.g., select and/orconfigure, which may be based on the physical layer measurement reportand/or the one or more RRC layer measurement report for cells) the atleast one first cell and/or the at least one second cell such that thefirst logical channel has better cell quality than the cell quality ofthe second logical channel. The base station DU may select the at leastone second cell for duplicated packets among secondary cells of thewireless device and/or among LAA cells. Each of the at least one secondcell may be different from any of the at least one first cell.

The base station DU, for example, may send, to the base station CU(e.g., via the F1 interface), a second message. The base station DU maysend the second message, for example, after or in response to the firstmessage. The second message may comprise, for example, a wireless device(e.g., UE) context setup response message, a wireless device (e.g., UE)context modification response message, a wireless device (e.g., UE)context modification required message, and/or the like. The secondmessage may comprise radio resource configuration parameters for thewireless device. The second message may comprise cell group information(e.g., CellGroupConfig, PhysicalCellGroupConfig, etc.). The radioresource configuration parameters may comprise: at least one first cellidentifier of the at least one first cell and for the first logicalchannel, and/or at least one second cell identifier of the at least onesecond cell and for the second logical channel The radio resourceconfiguration parameters may be included in the second message, such asin a DU To CU RRC Information IE, in an SRB Setup List IE, and/or in aDRB Setup List IE of the second message. The DU To CU RRC Information IEmay comprise RRC parameters that may be determined by the base stationDU for the wireless device.

The second message may not comprise the at least one first cellidentifier for the first logical channel and/or the at least one secondcell identifier for the second logical channel, for example, if the basestation CU determines the at least one first cells for the first logicalchannel and/or the at least one second cells for the second logicalchannel. The second message may indicate that the first bearer is setupfor the wireless device (e.g., by indicating that the base station DUallocates radio resources for the first bearer, by setting upPHY/MAC/RLC configuration parameters for the first bearer, and/or thelike). The second message may comprise at least one of a list of bearerssetup (e.g., comprising the first bearer), a list of bearers failed tobe setup, the wireless device identifier of the wireless device, and/orthe like.

The base station DU, for example, may receive, from the base station CU,an RRC message (e.g., an RRC connection reconfiguration message) for thewireless device. The RRC message may comprise the radio resourceconfiguration parameters. The base station DU may determine the radioresource configuration parameters comprising the at least one first cellidentifier for the first logical channel and/or the at least one secondcell identifier for the second logical channel, for example, if thesecond message does not comprise the at least one first cell identifierfor the first logical channel and/or the at least one second cellidentifier for the second logical channel. The base station DU mayreceive the RRC message, for example, via an F1 interface message (e.g.,a DL RRC message transfer message). An RRC-Container IE of the DL RRCmessage transfer message may comprise the RRC message. The base stationmay send the RRC message to the wireless device. The base station DU maysend the RRC message to the wireless device without interpretation(e.g., the base station DU may not decode the RRC message and/or one ormore elements of the RRC message).

The base station DU, for example, may receive a response RRC message(e.g., an RRC connection reconfiguration complete message) from thewireless device, for example, after or in response to the RRC message.The base station DU may send (e.g., forward, transmit, etc.) theresponse RRC message to the base station CU, for example, via an F1interface message (e.g., a UL RRC message transfer message).

The base station DU, for example, may receive, from the wireless devicevia the at least one first cell, first uplink transport blocksassociated with the first logical channel. The base station DU mayreceive, from the wireless device via the at least one second cell,second uplink transport blocks associated with the second logicalchannel. The base station DU may send, to the wireless device via the atleast one first cell, first downlink transport blocks associated withthe first logical channel. The base station DU and may send, to thewireless device via the at least one second cell, second downlinktransport blocks associated with the second logical channel.

FIG. 15 shows an example for cell configuration associated with uplinktransmissions. In step 1501, a base station CU 1551 (e.g., a gNB-CU),for example, may send (e.g., transmit), to a base station DU 1553 (e.g.,a gNB-DU), a first message. The first message may indicate, for example,bearer configuration parameters comprising PDCP duplication informationof a first bearer for a wireless device 1555 (e.g., a UE). The basestation DU 1553 may receive the first message. In step 1502, the basestation DU 1553 may determine, for example, one or more cells (e.g.,cell 1, cell 2, and/or cell 3) for a first logical channel of the firstbearer and/or one or more cells (e.g., cell 4 and/or cell 5) for asecond logical channel for duplications of PDCP packets of the firstlogical channel. The base station DU 1553 may determine the one or morecells for the first logical channel of the first bearer and/or the oneor more cells for the second logical channel for duplications of PDCPpackets of the first logical channel, for example, based on the firstmessage. In step 1503, the base station DU 1553 may send, to the basestation CU 1551, a second message. The second message may indicate thedetermined one or more cells for the first logical channel of the firstbearer and/or the determined one or more cells for the second logicalchannel of the first bearer. The second message may indicate cellidentifiers of cell 1, cell 2, and/or cell 3 for the first logicalchannel, and/or cell identifiers of cell 4 and/or cell 5 for the secondlogical channel. The base station CU 1551 may receive the secondmessage.

In step 1504, the base station CU 1551, for example, may send, to thebase station DU 1553, an RRC message. The RRC message may indicate, forexample, cell identifiers of cell 1, cell 2, and/or cell 3 for the firstlogical channel, and/or cell identifiers of cell 4 and/or cell 5 for thesecond logical channel. The base station DU 1553 may receive the RRCmessage. In step 1505, the base station DU 1553 may send, to thewireless device 1555, the RRC message. The wireless device 1555 mayreceive the RRC message. The wireless device 1555 may, for example,configure the one or more cells for the first logical channel (e.g.,cell 1, cell 2, and/or cell 3) and/or the one or more cells for thesecond logical channel (e.g., cell 4 and/or cell 5). The first logicalchannel, the second logical channel, and/or the cell(s) for the firstlogical channel and/or the second logical channel may be configured foruplink communications. The wireless device 1555 may send, to the basestation DU 1553 via cell 1, cell 2, and/or cell 3, first transportblocks. The wireless device 1555 may send, to the base station DU 1553via cell 4 and/or cell 5, second transport blocks (e.g., duplications ofthe first transport blocks).

FIG. 16 shows an example for cell configuration associated with downlinktransmissions. The processes shown in FIG. 16 may be performed in asimilar manner as the processes discussed in connection with FIG. 15. Afirst logical channel, a second logical channel, and/or cell(s) for thefirst logical channel and/or the second logical channel may beconfigured by a base station CU 1651, a base station DU 1653, and/or awireless device 1655, and/or may be configured for downlinkcommunications. The wireless device 1655 may receive, from the basestation DU 1653 via cell 1, cell 2, and/or cell 3, first transportblocks. The wireless device 1655 may receive, from the base station DU1653 via cell 4 and/or cell 5, second transport blocks (e.g.,duplications of the first transport blocks).

FIG. 17 is a diagram showing an example method for cell configuration.The method may be performed, for example, by a wireless device (e.g.,the wireless devices 1555, 1655), a base station DU (e.g., the basestation DUs 1553, 1653), and/or a base station CU (e.g., the basestation CUs 1551, 1651). In step 1701, the base station CU, for example,may send, to the base station DU, a first message. The first message mayindicate, for example, bearer configuration parameters comprising PDCPduplication information of a first bearer for the wireless device. Thebase station DU may receive the first message. In step 1702, the basestation DU may determine, for example, at least one first cell for afirst logical channel and at least one second cell for a second logicalchannel for duplications of PDCP packets of the first logical channel.The base station DU may determine the at least one first cell for thefirst logical channel and the at least one second cell for the secondlogical channel for duplications of PDCP packets of the first logicalchannel, based on the first message. In step 1703, the base station DUmay send, to the base station CU, a second message. The second messagemay indicate, for example, at least one first cell identifier of the atleast one first cell for the first logical channel, and at least onesecond cell identifier of the at least one second cell for the secondlogical channel. The base station CU may receive the second message. Instep 1704, the base station CU may send, to the base station DU, an RRCmessage. The RRC message may indicate, for example, the at least onefirst cell identifier for the first logical channel, and the at leastone second cell identifier for the second logical channel. The basestation DU may receive the RRC message. In step 1705, the base stationDU may send, to the wireless device, the RRC message.

FIG. 18 shows an example for cell configuration associated with uplinktransmissions. In step 1801, a base station CU 1851 (e.g., a gNB-CU),for example, may send, to a base station DU 1853 (e.g., a gNB-DU), afirst message. The first message may indicate, for example, bearerconfiguration parameters comprising cell identifier(s) of one or morecells (e.g., cell 1, cell 2, and/or cell 3) for a first logical channelof a first bearer for a wireless device 1855 (e.g., a UE), and cellidentifier(s) of one or more cells (e.g., cell 4 and/or cell 5) for asecond logical channel for duplications of PDCP packets of the firstlogical channel. The base station DU 1853 may receive the first message.In step 1802, the base station DU 1853 may configure the one or morecells for the first logical channel (e.g., cell 1, cell 2, and/or cell3) and the one or more cells for the second logical channel (e.g., cell4 and/or cell 5). The base station DU 1853 may configure the one or morecells for the first logical channel and the one or more cells for thesecond logical channel, for example, based on the first message. In step1803, the base station DU 1853 may send, to the base station CU 1851, asecond message. The second message may indicate, for example, that thefirst bearer (e.g., including the cell(s) for the logical channel(s) ofthe first bearer) is setup. The base station CU 1851 may receive thesecond message.

In step 1804, the base station CU 1851, for example, may send, to thebase station DU 1853, an RRC message. The RRC message may indicate, forexample, cell identifiers of cell 1, cell 2, and/or cell 3 for the firstlogical channel, and/or cell identifiers of cell 4 and/or cell 5 for thesecond logical channel. The base station DU 1853 may receive the RRCmessage. In step 1805, the base station DU 1853 may send, to thewireless device 1855, the RRC message. The wireless device 1855 mayreceive the RRC message. The wireless device 1855 may, for example,configure the one or more cells for the first logical channel (e.g.,cell 1, cell 2, and/or cell 3) and/or the one or more cells for thesecond logical channel (e.g., cell 4 and/or cell 5). The first logicalchannel, the second logical channel, and/or the cell(s) for the firstlogical channel and/or the second logical channel may be configured foruplink communications. The wireless device 1855 may send, to the basestation DU 1853 via cell 1, cell 2, and/or cell 3, first transportblocks. The wireless device 1855 may send, to the base station DU 1853via cell 4 and/or cell 5, second transport blocks (e.g., duplications ofthe first transport blocks).

FIG. 19 shows an example for cell configuration associated with downlinktransmissions. The processes shown in FIG. 19 may be performed in asimilar manner as the processes discussed in connection with FIG. 18. Afirst logical channel, a second logical channel, and/or cell(s) for thefirst logical channel and/or the second logical channel may beconfigured by a base station CU 1951, a base station DU 1953, and/or awireless device 1955, and may be configured for downlink communications.The wireless device 1955 may receive, from the base station DU 1953 viacell 1, cell 2, and/or cell 3, first transport blocks. The wirelessdevice 1955 may receive, from the base station DU 1953 via cell 4 and/orcell 5, second transport blocks (e.g., duplications of the firsttransport blocks).

FIG. 20 is a diagram showing an example method for cell configuration.The method may be performed, for example, by a wireless device (e.g.,the wireless devices 1855, 1955), a base station DU (e.g., the basestation DUs 1853, 1953), and/or a base station CU (e.g., the basestation CUs 1851, 1951). In step 2001, the base station CU, for example,may send, to the base station DU, a first message. The first message mayindicate, for example, bearer configuration parameters comprising atleast one first cell identifier of at least one first cell for a firstlogical channel of a first bearer for the wireless device, and at leastone second cell identifier of at least one second cell for a secondlogical channel for duplications of PDCP packets of the first logicalchannel. The base station DU may receive the first message. In step2002, the base station DU may configure the at least one first cell forthe first logical channel and the least one second cell for the secondlogical channel. The base station DU may configure the at least onefirst cell for the first logical channel and the least one second cellfor the second logical channel, for example, based on the first message.In step 2003, the base station DU may send, to the base station CU, asecond message. The second message may indicate, for example, that thefirst bearer (e.g., including the cell(s) for the logical channel(s) ofthe first bearer) is setup. The base station CU may receive the secondmessage. In step 2004, the base station CU may send, to the base stationDU, an RRC message. The RRC message may indicate, for example, the atleast one first cell identifier for the first logical channel, and theat least one second cell identifier for the second logical channel. Thebase station DU may receive the RRC message. In step 2005, the basestation DU may send, to the wireless device, the RRC message.

FIG. 21 shows an example method for cell configuration that may beperformed, for example, by a base station CU. In step 2101, a basestation CU may determine that PDCP duplication is configured for abearer of a wireless device (e.g., a UE). The determination may be basedon, for example, quality of service (QoS) requirements associated withthe bearer, service types associated with the bearer, network slicesassociated with the bearer, downlink/uplink radio channel conditionsassociated with the bearer, and/or previous base station'sconfigurations of the bearer. If a bearer is used for URLLC servicesand/or other services (e.g., high priority services), the base stationCU may determine that PDCP duplication is configured for the bearer. Instep 2103, the base station CU may determine whether the wireless deviceis configured with multiple serving cells (e.g., for carrieraggregation). If the base station CU determines that the wireless deviceis configured with multiple serving cells (step 2103: Yes), the methodmay proceed to step 2105. If the base station CU determines that thewireless device is not configured with multiple service cells (step2103: No), the method may end.

In step 2105, the base station CU may determine cell(s) for logicalchannel(s) of the bearer. The base station CU may determine, forexample, first cell(s) for a first logical channel of the bearer andsecond cell(s) for a second logical channel for duplications of packetsof the first logical channel. The determination may be based on, forexample, a measurement report received from the wireless device via oneor more RRC messages. In step 2107, the base station CU may send, to abase station DU, bearer configuration parameters comprising cellidentifier(s) of the cell(s), as determined in step 2105, for thelogical channel(s) of the bearer. The bearer configuration parametersmay comprise, for example, first cell identifier(s) (e.g., cell index)of the first cell(s) for the first logical channel, and second cellidentifier(s) (e.g., cell index) of the second cell(s) for the secondlogical channel.

In step 2109, the base station CU may determine whether a bearer setupindication associated with the bearer is received from the base stationDU. The bearer setup indication may indicate, for example, that thefirst cell(s) for the first logical channel and the second cell(s) forthe second logical channel is configured by the base station DU. Thebearer setup indication may additionally or alternatively indicatephysical layer parameters associated with the configured cell(s) (e.g.,the first cell(s) and/or the second cell(s)). If the base station CUdetermines that it has received a bearer setup indication associatedwith the bearer (step 2109: Yes), the method may proceed to step 2111.If the base station CU determines that it has not received a bearersetup indication associated with the bearer (step 2109: No), the methodmay end.

In step 2111, the base station CU may send, to the wireless device andvia the base station DU, RRC message(s). The RRC message(s) mayindicate, for example, configuration parameters comprising the firstcell identifier(s) for the first logical channel and the second cellidentifier(s) for the second logical channel. In step 2113, the basestation CU may receive, from the wireless device, RRC responsemessage(s) indicating that the cell(s) have been configured by thewireless device based on the configuration parameters (e.g., indicatedin the RRC message(s)).

In step 2115, the base station CU may determine whether uplink packetsassociated with the wireless device are received from the base stationDU (e.g., via the first logical channel) and/or whether duplications ofthe uplink packets associated with the wireless device are received fromthe base station DU (e.g., via the second logical channel). If the basestation CU determines it has received the uplink packets and theduplications of the uplink packets (step 2115: Yes), the method mayproceed to step 2117. If the base station CU determines it has notreceived the uplink packets and the duplications of the uplink packets(step 2115: No), the method may proceed to step 2119. In step 2117, thebase station CU may discard at least one of the received uplink packetsor the received corresponding duplications (e.g., in order tode-duplicate the received packets). The base station CU may send (e.g.,forward, transmit, etc.), to a User Plane Function (UPF) (e.g., of acore network), the de-duplicated uplink packets associated with thewireless device.

In step 2119, the base station CU may determine whether downlink packetsassociated with the bearer are received from the UPF. If the basestation CU determines that it has received the downlink packets from theUPF (step 2119: Yes), the method may proceed to step 2121. If the basestation CU determines that it has not received the downlink packets fromthe UPF (step 2119: No), the method may end. In step 2121, the basestation CU may duplicate the downlink packets associated with thebearer. The base station CU may, for example, send (e.g., forward,transmit, etc.), to the wireless device, via the base station DU, andvia the first logical channel, the downlink packets. The base station CUmay send (e.g., forward, transmit, etc.), to the wireless device, viathe base station DU, and via the second logical channel, theduplications of the downlink packets.

FIG. 22 shows an example method for cell configuration that may beperformed, for example, by a base station CU. In step 2201, a basestation CU may determine that PDCP duplication is configured for abearer of a wireless device (e.g., a UE). The determination may be basedon, for example, QoS requirements associated with the bearer, servicetypes associated with the bearer, network slices associated with thebearer, downlink and/or uplink radio channel conditions associated withthe bearer, and/or a previous base station's configurations of thebearer. If a bearer is used for URLLC services and/or other services(e.g., high priority services), the base station CU may determine thatPDCP duplication is configured for the bearer. In step 2203, the basestation CU may determine whether the wireless device is configured withmultiple serving cells (e.g., carrier aggregation). If the base stationCU determines that the wireless device is configured with multipleserving cells (step 2203: Yes), the method may proceed to step 2205. Ifthe base station CU determines that the wireless device is notconfigured with multiple serving cells (step 2203: No), the method mayend.

In step 2205, the base station CU may send, to a base station DU,parameter(s) indicating that PDCP duplication is configured for thebearer of the wireless device. In step 2207, the base station CU maydetermine whether a bearer setup indication associated with the beareris received from the base station DU. The bearer setup indication mayindicate, for example, that the bearer (e.g., including logicalchannel(s) and/or cell(s) associated with the bearer) is configured bythe base station DU. If the base station CU determines that it hasreceived the bearer setup indication (step 2207: Yes), the method mayproceed to step 2209. If the base station CU determines that it has notreceived the bearer setup indication (step 2207: No), the method mayend. In step 2209, the base station CU may determine whether the bearersetup indication indicates bearer configuration parameters associatedwith the bearer, such as first cell identifier(s) (e.g., cell index) offirst cell(s) for a first logical channel of the bearer and second cellidentifier(s) (e.g., cell index) of second cell(s) for a second logicalchannel for duplications of packets of the first logical channel. If thebase station CU determines that the bearer setup indication indicatesthe bearer configuration parameters associated with the bearer (step2209: Yes), the method may proceed to step 2211. If the base station CUdetermines that the bearer setup indication does not indicate the bearerconfiguration parameters associated with the bearer (step 2209: Yes),the method may end.

In step 2211, the base station CU may send, to the wireless device andvia the base station DU, RRC message(s). The RRC message(s) mayindicate, for example, configuration parameters comprising the firstcell identifier(s) for the first logical channel, and the second cellidentifier(s) for the second logical channel. In step 2213, the basestation CU may receive, from the wireless device, RRC responsemessage(s) indicating that the cell(s) have been configured by thewireless device based on the configuration parameters (e.g., indicatedin the RRC message(s)).

In step 2215, the base station CU may determine whether uplink packetsassociated with the wireless device are received from the base stationDU (e.g., via the first logical channel) and/or whether duplications ofthe uplink packets associated with the wireless device are received fromthe base station DU (e.g., via the second logical channel). If the basestation CU determines that it has received the uplink packets and theduplications of the uplink packets (step 2215: Yes), the method mayproceed to step 2217. If the base station CU determines that it has notreceived the uplink packets and the duplications of the uplink packets(step 2215: No), the method may proceed to step 2219. In step 2217, thebase station CU may discard at least one of the received uplink packetsor the received corresponding duplications (e.g., in order tode-duplicate the received packets). The base station CU may send (e.g.,forward, transmit, etc.), to a UPF (e.g., of a core network), thede-duplicated uplink packets associated with the wireless device.

In step 2219, the base station CU may determine whether downlink packetsassociated with the bearer are received from the UPF. If the basestation CU determines that it has received the downlink packets from theUPF (step 2219: Yes), the method may proceed to step 2221. If the basestation CU determines that it has not received the downlink packets fromthe UPF (step 2219: No), the method may end. In step 2221, the basestation CU may duplicate the downlink packets associated with thebearer. The base station CU may, for example, send (e.g., forward,transmit, etc.), to the wireless device, via the base station DU, andvia the first logical channel, the downlink packets. The base station CUmay send (e.g., forward, transmit, etc.), to the wireless device, viathe base station DU, and via the second logical channel, theduplications of the downlink packets.

FIG. 23 shows an example method for cell configuration that may beperformed, for example, by a base station DU. In step 2301, a basestation DU may configure multiple serving cells (e.g., carrieraggregation) for a wireless device. In step 2303, the base station DUmay determine whether bearer configuration parameters indicating PDCPduplication for a bearer for the wireless device are received from abase station CU. If the base station DU determines that it has receivedsuch bearer configuration parameters (step 2303: Yes), the method mayproceed to step 2305. If the base station DU determines that it has notreceived such bearer configuration parameters (step 2303: No), themethod may end. In step 2305, the base station DU may determine whetherthe received bearer configuration parameters comprise cell identifier(s)for the bearer. The bearer configuration parameters may comprise firstcell identifier(s) (e.g., cell index) of first cell(s) for a firstlogical channel of the bearer, and second cell identifier(s) (e.g., cellindex) of second cell(s) for a second logical channel for duplicationsof packets of the first logical channel. If the base station DUdetermines that it has received bearer configuration parameterscomprising cell identifier(s) for the bearer (step 2305: Yes), themethod may proceed to step 2307. If the base station DU determines thatit has not received bearer configuration parameters comprising cellidentifier(s) for the bearer (step 2305: No), the method may end.

In step 2307, the base station DU may configure cell(s) associated withthe bearer. The base station DU may configure the first cell(s) for thefirst logical channel, and the second cell(s) for the second logicalchannel. In step 2309, the base station DU may send, to the base stationCU, a bearer setup indication associated with the bearer. The bearersetup indication may indicate, for example, that the first cell(s) forthe first logical channel and the second cell(s) for the second logicalchannel are configured by the base station DU. The bearer setupindication may additionally or alternatively indicate physical layerparameters associated with the configured cell(s) (e.g., the firstcell(s) and/or the second cell(s)).

In step 2311, the base station DU may receive, from the base station CU,RRC message(s). The RRC message(s) may indicate, for example,configuration parameters comprising the first cell identifier(s) for thefirst logical channel and the second cell identifier(s) for the secondlogical channel. The base station DU may send (e.g., forward, transmit,etc.), to the wireless device, the RRC message(s). In step 2313, thebase station DU may receive, from the wireless device, RRC responsemessage(s). The RRC response message(s) may indicate, for example, thecell(s) have been configured by the wireless device based on theconfiguration parameters (e.g., indicated in the RRC message(s)). Thebase station DU may send (e.g., forward, transmit, etc.), to the basestation CU, the RRC response message(s).

In step 2315, the base station DU may determine whether uplink packetsare received from the wireless device (e.g., via the first logicalchannel and/or the first cell(s)), and whether duplications of theuplink packets are received from the wireless device (e.g., via thesecond logical channel and/or the second cell(s)). If the base stationDU determines that it has received the uplink packets and theduplications of the uplink packets (step 2315: Yes), the method mayproceed to step 2317. If the base station DU determines that it has notreceived the uplink packets and the duplications of the uplink packets(step 2315: No), the method may proceed to step 2319. Additionally oralternatively, the base station DU may determine whether a PDCPduplication activation indication for the bearer is sent (e.g., from thebase station DU) to the wireless device. If the base station DUdetermines that such an indication is sent, the method may proceed tostep 2317. If the base station DU determines that such an indication isnot sent, the method may proceed to step 2319.

In step 2317, the base station DU may send (e.g., forward, transmit,etc.), to the base station CU (e.g., via a first tunnel for the firstlogical channel), the uplink packets; and the base station DU may send(e.g., forward, transmit, etc.), to the base station CU (e.g., via asecond tunnel for the second logical channel), the duplications of theuplink packets. In step 2319, the base station DU may determine whetherdownlink packets associated with the wireless device are received fromthe base station CU (e.g., via the first tunnel for the first logicalchannel), and whether duplications of the downlink packets associatedwith the wireless device are received from the base station CU (e.g.,via the second tunnel for the second logical channel. If the basestation DU determines that is has received the downlink packets and theduplications of the downlink packets (step 2319: Yes), the method mayproceed to step 2321. If the base station DU determines that it has notreceived the downlink packets and the duplications of the downlinkpackets (step 2319: No), the method may end. In step 2321, the basestation DU may send (e.g., forward, transmit, etc.), to the wirelessdevice (e.g., via the first logical channel and/or the first cell(s)),the downlink packets; and the base station DU may send (e.g., forward,transmit, etc.), to the wireless device (e.g., via the second logicalchannel and/or the second cell(s)), the duplications of the downlinkpackets.

FIG. 24 shows an example method for cell configuration that may beperformed, for example, by a base station DU. In step 2401, a basestation DU may configure multiple serving cells (e.g., carrieraggregation) for a wireless device. In step 2403, the base station DUmay determine whether bearer configuration parameters indicating PDCPduplication for a bearer for the wireless device are received from abase station CU. If the base station DU determines that it has receivedsuch bearer configuration parameters (step 2403: Yes), the method mayproceed to step 2405. If the base station DU determines that it has notreceived such bearer configuration parameters (step 2403: No), themethod may end. In step 2405, the base station DU may determine and/orconfigure cell(s) for logical channel(s) of the bearer. The base stationDU may determine and/or configure: first cell(s) for a first logicalchannel of the bearer, and second cell(s) for a second logical channelfor duplications of packets of the first logical channel. Thedetermination may be, for example, based on: a channel stationinformation report, associated with the cell(s), received from thewireless device; on a measurement result of one or more soundingreference signals, associated with the cell(s), received from thewireless device; and/or the like.

In step 2407, the base station DU may send, to the base station CU, abearer setup indication associated with the bearer. The bearer setupindication may indicate, for example, that the bearer is configured bythe base station DU. The bearer setup indication may additionally oralternatively indicate bearer configuration parameters comprising cellidentifier(s) for the bearer. The bearer configuration parameters maycomprise: first cell identifier(s) (e.g., cell index) of the firstcell(s) for the first logical channel, and second cell identifier(s)(e.g., cell index) of the second cell(s) for the second logical channel.

In step 2409, the base station DU may receive, from the base station CU,RRC message(s). The RRC message(s) may indicate, for example,configuration parameters comprising: the first cell identifier(s) forthe first logical channel, and the second cell identifier(s) for thesecond logical channel. The base station DU may send (e.g., forward,transmit, etc.), to the wireless device, the RRC message(s). In step2411, the base station DU may receive, from the wireless device, RRCresponse message(s). The RRC response message(s) may indicate, forexample, the cell(s) have been configured by the wireless device basedon the configuration parameters (e.g., indicated in the RRC message(s)).The base station DU may send (e.g., forward, transmit, etc.), to thebase station CU, the RRC response message(s).

In step 2413, the base station DU may determine whether uplink packetsare received from the wireless device (e.g., via the first logicalchannel and/or the first cell(s)), and whether duplications of theuplink packets are received from the wireless device (e.g., via thesecond logical channel and/or the second cell(s)). If the base stationDU determines that it has receive the uplink packets and theduplications of the uplink packets (step 2413: Yes), the method mayproceed to step 2415. If the base station DU determines that it has notreceived the uplink packets and the duplications of the uplink packets(step 2413: No), the method may proceed to step 2417. Additionally oralternatively, the base station DU may determine whether a PDCPduplication activation indication for the bearer is sent (e.g., from thebase station DU) to the wireless device. If the base station DUdetermines that such an indication is sent, the method may proceed tostep 2415. If the base station DU determines that such an indication isnot sent, the method may proceed to step 2417.

In step 2415, the base station DU may send (e.g., forward, transmit,etc.), to the base station CU (e.g., via a first tunnel for the firstlogical channel), the uplink packets; and the base station DU may send(e.g., forward, transmit), to the base station CU (e.g., via a secondtunnel for the second logical channel), the duplications of the uplinkpackets. In step 2417, the base station DU may determine whetherdownlink packets associated with the wireless device are received fromthe base station CU (e.g., via the first tunnel for the first logicalchannel), and whether duplications of the downlink packets associatedwith the wireless device are received from the base station CU (e.g.,via the second tunnel for the second logical channel). If the basestation DU determines that it has received the downlink packets and theduplications of the downlink packets (step 2417: Yes), the method mayproceed to step 2419. If the base station DU determines that it has notreceived the downlink packets and the duplications of the downlinkpackets (step 2417: No), the method may end. In step 2419, the basestation DU may send (e.g., forward, transmit, etc.), to the wirelessdevice (e.g., via the first logical channel and/or the first cell(s)),the downlink packets; and the base station DU may send (e.g., forward,transmit, etc.), to the wireless device (e.g., via the second logicalchannel and/or the second cell(s)), the duplications of the downlinkpackets.

FIG. 25 shows an example method for cell configuration that may beperformed, for example, by a wireless device. In step 2501, a wirelessdevice may configure itself with multiple serving cells (e.g., carrieraggregation). In step 2503, the wireless device may receive, from a basestation CU (e.g., via a base station DU), RRC message(s). The RRCmessage(s) may comprise, for example, configuration parameters. Theconfiguration parameters may comprise: first cell identifier(s) (e.g.,cell index) of first cell(s) for a first logical channel of a bearer forthe wireless device, and second cell identifier(s) (e.g., cell index) ofsecond cell(s) for a second logical channel for duplications of packetsof the first logical channel. In step 2505, the wireless device mayconfigure the cell(s) for the bearer for the wireless device. Thewireless device may configure, based on the RRC message(s), the firstcell(s) for the first logical channel and the second cell(s) for thesecond logical channel.

In step 2507, the wireless device may send, to the base station CU(e.g., via the base station DU), RRC response message(s). The RRCresponse message(s) may indicate, for example, that the cell(s) for thebearer have been configured by the wireless device based on theconfiguration parameters (e.g., indicated in the RRC message(s)). Instep 2509, the wireless device may determine whether a PDCP duplicationactivation indication associated with the bearer for the wireless deviceis received (e.g., from the base station CU and/or the base station DU).If the wireless device determines that a PDCP duplication activationindication associated with the bearer for the wireless device isreceived (step 2509: Yes), the method may proceed to step 2511. If thewireless device determines that a PDCP duplication activation indicationassociated with the bearer for the wireless device is not received (step2509: No), the method may proceed to step 2515. Additionally oralternatively, the wireless device may determine whether the wirelessdevice has uplink packets, associated with the bearer, to be sent. Ifthe wireless device determines that it has such uplink packets to besent, the method may proceed to step 2511. If the wireless devicedetermines that it does not have such uplink packets to be sent, themethod may proceed to step 2515.

In step 2511, the wireless device may duplicate the uplink packets,associated with the bearer, to be sent. The wireless device may generateduplications of the uplink packets. In step 2513, the wireless devicemay send, to the base station CU (e.g., via the base station DU) and viathe first logical channel and/or the first cell(s), the uplink packets;and the wireless device may send, to the base station CU (e.g., via thebase station DU) and via the second logical channel and/or the secondcell(s), the duplications of the uplink packets. In step 2515, thewireless device may receive, from the base station CU (e.g., via thebase station DU) and via the first logical channel and/or the firstcell(s), downlink packets; and the wireless device may receive, from thebase station CU (e.g., via the base station DU) and via the secondlogical channel and/or the second cell(s), duplications of the downlinkpackets. In step 2517, the wireless device may discard at least one ofthe received downlink packets or the received duplications of thedownlink packets (e.g., in order to de-duplicate the received packets).

A base station DU may receive, from a base station CU, a first messagecomprising bearer configuration parameters of a bearer for a wirelessdevice. The bearer configuration parameters may comprise a firstparameter indicating that packet duplication is configured for thebearer, at least one first cell index of at least one first cell for afirst logical channel, and at least one second cell index of at leastone second cell for a second logical channel. The second logical channelmay be for duplications of packet data convergence protocol packets ofthe first logical channel. The base station DU may send, to the basestation CU, a second message comprising first physical layer parametersfor the at least one first cell and second physical layer parameters forthe at least one second cell. The base station DU may receive, from thebase station CU, a radio resource control message comprisingconfiguration parameters for the wireless device. The configurationparameters may comprise the bearer configuration parameters, the firstphysical layer parameters, and the second physical layer parameters. Thebase station DU may send, to the wireless device, the radio resourcecontrol message.

The base station DU may send, to the wireless device: first transportblocks of the first logical channel via the at least one first cell, andsecond transport blocks of the second logical channel via the at leastone second cell. The base station DU may receive, from the wirelessdevice: first transport blocks of the first logical channel via the atleast one first cell, and second transport blocks of the second logicalchannel via the at least one second cell. The base station DU may send,to the wireless device, the radio resource control message withoutinterpretation. The radio resource control message may comprise a radioresource control reconfiguration message. The at least one first cellmay be different from the at least one second cell. The bearerconfiguration parameters may further comprise at least one of a firstlogical channel index of the first logical channel and a second logicalchannel index of the second logical channel.

The first message may further comprise: a first tunnel endpointidentifier of a first tunnel for the first logical channel, and a secondtunnel endpoint identifier of a second tunnel for the second logicalchannel. The base station DU may send, to the base station CU packets ofthe first logical channel via the first tunnel, and packets of thesecond logical channel via the second tunnel. The base station DU mayreceive, from the base station CU: packets of the first logical channelvia the first tunnel, and packets of the second logical channel via thesecond tunnel. The first message may further comprise at least one of: aparameter indicating that the first logical channel comprises anoriginal logical channel of the first bearer, and/or a parameterindicating that the second logical channel is for duplicated packets ofthe first bearer. The second message may comprise at least one of: atleast one third cell index of at least one third cell for the firstlogical channel, and/or at least one fourth cell index of at least onefourth cell for the second logical channel. The base station DU maydetermine the at least one third cell or the at least one fourth cell,based on at least one of: a channel state information report receivedfrom the wireless device, or a measurement result of one or moresounding reference signals received from the wireless device. The basestation DU may send a medium access control (MAC) control element (CE)indicating an activation of the packet duplication for the bearer. Thebase station DU may send a MAC CE indicating a deactivation of thepacket duplication for the bearer.

The base station CU may receive, from the wireless device, at least onemeasurement report comprising measurement results of: the at least onefirst cell, and/or the at least one second cell. The measurement resultsmay comprise at least one of: a reference signal received power, and/ora reference signal received quality. The base station CU may determine,for example, based on the at least one measurement report, the packetduplication for the bearer. The at least one second cell may comprise alicensed assisted access cell. The second message may indicate that thebearer is configured for the wireless device. The base station DU mayreceive the radio resource control message via a downlink radio resourcecontrol message transfer message. The base station CU may comprise: atleast one of a radio resource control layer function, a packet dataconvergence protocol layer function, or a service data adaptationprotocol layer function. The base station DU may comprise at least oneof: a physical layer function, a medium access control layer function,and/or a radio link control layer function.

A base station DU may receive, from a base station CU, a first messagecomprising bearer configuration parameters of a bearer for a wirelessdevice. The bearer configuration parameters may comprise: a firstparameter indicating that packet duplication is configured for thebearer, at least one first cell index of at least one first cell for afirst logical channel, and/or at least one second cell index of at leastone second cell for a second logical channel. The second logical channelmay be for duplications of packet data convergence protocol packets ofthe first logical channel. The base station DU may send, to the basestation CU, a second message indicating that the bearer is configured bythe base station DU. The base station DU may receive, from the basestation CU, a radio resource control message comprising configurationparameters for the wireless device. The configuration parameters maycomprise: the at least one first cell index for the first logicalchannel, and the at least one second cell index for the second logicalchannel. The base station DU may send, to the wireless device, the radioresource control message.

A base station CU may determine packet duplication for a bearer for awireless device. The base station CU may send, to a base station DU, afirst message comprising bearer configuration parameters of the bearerfor the wireless device. The bearer configuration parameters maycomprise: a first parameter indicating that the packet duplication isconfigured for the bearer, at least one first cell index of at least onefirst cell for a first logical channel, and/or at least one second cellindex of at least one second cell for a second logical channel. Thesecond logical channel may be for duplications of packet dataconvergence protocol packets of the first logical channel. The basestation CU may receive, from the base station DU, a second messagecomprising: first physical layer parameters for the at least one firstcell, and/or second physical layer parameters for the at least onesecond cell. The base station CU may send, to the wireless device viathe base station DU, a radio resource control message comprisingconfiguration parameters for the wireless device. The configurationparameters may comprise the bearer configuration parameters, the firstphysical layer parameters, and/or the second physical layer parameters.

A base station DU may receive, from a base station CU, a first messagecomprising bearer configuration parameters for a wireless device. Thebearer configuration parameters may comprise at least one of: a firstbearer identifier of a first bearer, and/or a PDCP duplicationinformation for the first bearer. The base station DU may determine,based on the bearer configuration parameters, at least one first cell tobe used for a first logical channel of the first bearer, and/or at leastone second cell to be used for a second logical channel for duplicationsof PDCP packets of the first logical channel. The base station DU maysend, to the base station CU, a second message comprising radio resourceconfiguration parameters for the wireless device. The radio resourceconfiguration parameters may comprise at least one: first cellidentifier of the at least one first cell and for the first logicalchannel, and/or at least one second cell identifier of the at least onesecond cell and for the second logical channel. The base station DU mayreceive, from the base station CU, an RRC message comprising the radioresource configuration parameters. The base station DU may send, to thewireless device, the RRC message.

The base station DU may receive/send, from/to the wireless device: firsttransport blocks associated with the first logical channel, and/orsecond transport blocks associated with the second logical channel. Thebase station DU may receive/send: the first transport blocks via the atleast one first cell, and/or the second transport blocks via the atleast one second cell. The base station DU may send, to the wirelessdevice, the RRC message without interpretation. The RRC message may bean RRC connection reconfiguration message. Each of the at least onesecond cell may be different from any of the at least one first cell.

The PDCP duplication information may comprise at least one of: at leastone logical channel information element (IE) (e.g., comprising the firstlogical channel identifier of the first logical channel of the firstbearer, and/or the second logical channel identifier of the secondlogical channel for duplications of PDCP packets of the first logicalchannel), and/or a PDCP duplication indication IE indicating that PDCPpackets of the first bearer are duplicated. The first message maycomprise: a first tunnel endpoint identifier of a first tunnel for thefirst logical channel, and/or a second tunnel endpoint identifier of asecond tunnel for the second logical channel. The base station DU maysend, to the base station CU: the first transport blocks via the firsttunnel, and/or the second transport blocks via the second tunnel. Thefirst message may further comprise at least one of: a first informationelement (IE) indicating the first logical channel is a default logicalchannel of the first bearer, and/or a second IE indicating the secondlogical channel is for duplicated PDCP packet transmissions of the firstbearer.

A base station DU may receive, from a base station CU, a first messagecomprising bearer configuration parameters for the wireless device. Thebearer configuration parameters may comprise at least one of: a firstbearer identifier of a first bearer, a PDCP duplication information forthe first bearer, at least one first cell identifier of at least onefirst cell used for a first logical channel of the first bearer, and/orat least one second cell identifier of at least one second cell used fora second logical channel for duplications of PDCP packets of the firstlogical channel. The base station DU may configure the at least onefirst cell for the first logical channel and the at least one secondcell for the second logical channel. The base station DU may send, tothe base station CU, a second message indicating that the first beareris setup. The base station DU may receive, from the base station CU, anRRC message comprising radio resource configuration parameters for thewireless device. The radio resource configuration parameters maycomprise: the at least one: first cell identifier for the first logicalchannel, and/or the at least one second cell identifier for the secondlogical channel. The base station DU may send, to the wireless device,the RRC message.

The base station DU may receive/send, from/to the wireless device: firsttransport blocks associated with the first logical channel, and/orsecond transport blocks associated with the second logical channel. Thebase station DU may receive/send: the first transport blocks via the atleast one first cell, and/or the second transport blocks via the atleast one second cell. The base station DU may send, to the wirelessdevice, the RRC message without interpretation. The RRC message may bean RRC connection reconfiguration message. Each of the at least onesecond cell may be different from any of the at least one first cell.

The PDCP duplication information may comprise at least one of: at leastone logical channel information element (IE) (e.g., comprising the firstlogical channel identifier of the first logical channel of the firstbearer, and/or the second logical channel identifier of the secondlogical channel for duplications of PDCP packets of the first logicalchannel), and/or a PDCP duplication indication IE indicating that PDCPpackets of the first bearer are duplicated. The first message maycomprise: a first tunnel endpoint identifier of a first tunnel for thefirst logical channel, and/or a second tunnel endpoint identifier of asecond tunnel for the second logical channel. The base station DU maysend, to the base station CU: the first transport blocks via the firsttunnel, and/or the second transport blocks via the second tunnel. Thefirst message may further comprise at least one of: a first informationelement (IE) indicating that the first logical channel comprises adefault logical channel of the first bearer, and/or a second IEindicating that the second logical channel is for duplicated PDCP packettransmissions of the first bearer.

FIG. 26 shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, e.g.,the base station 401, the wireless device 406, or any other basestation, wireless device, or computing device described herein. Thecomputing device 2600 may include one or more processors 2601, which mayexecute instructions stored in the random access memory (RAM) 2603, theremovable media 2604 (such as a Universal Serial Bus (USB) drive,compact disk (CD) or digital versatile disk (DVD), or floppy diskdrive), or any other desired storage medium. Instructions may also bestored in an attached (or internal) hard drive 2605. The computingdevice 2600 may also include a security processor (not shown), which mayexecute instructions of one or more computer programs to monitor theprocesses executing on the processor 2601 and any process that requestsaccess to any hardware and/or software components of the computingdevice 2600 (e.g., ROM 2602, RAM 2603, the removable media 2604, thehard drive 2605, the device controller 2607, a network interface 2609, aGPS 2611, a Bluetooth interface 2612, a Wi-Fi interface 2613, etc.). Thecomputing device 2600 may include one or more output devices, such asthe display 2606 (e.g., a screen, a display device, a monitor, atelevision, etc.), and may include one or more output device controllers2607, such as a video processor. There may also be one or more userinput devices 2608, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 2600 may also include oneor more network interfaces, such as a network interface 2609, which maybe a wired interface, a wireless interface, or a combination of the two.The network interface 2609 may provide an interface for the computingdevice 2600 to communicate with a network 2610 (e.g., a RAN, or anyother network). The network interface 2609 may include a modem (e.g., acable modem), and the external network 2610 may include communicationlinks, an external network, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network. Additionally, thecomputing device 2600 may include a location-detecting device, such as aglobal positioning system (GPS) microprocessor 2611, which may beconfigured to receive and process global positioning signals anddetermine, with possible assistance from an external server and antenna,a geographic position of the computing device 2600.

The example in FIG. 26 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2600 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2601, ROM storage 2602, display 2606, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 26.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, Wi-Fi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, e.g.,any complementary step or steps of one or more of the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

1. A method comprising: sending, by a base station distributed unit to abase station central unit, a message comprising: at least one first cellindex of at least one first cell for a first logical channel; and atleast one second cell index of at least one second cell for a secondlogical channel, wherein the second logical channel is for packetduplication associated with the first logical channel; receiving, by thebase station distributed unit from the base station central unit, aradio resource control message comprising configuration parameters for awireless device, wherein the configuration parameters comprise: the atleast one first cell index of the at least one first cell for the firstlogical channel; and the at least one second cell index of the at leastone second cell for the second logical channel; and sending, by the basestation distributed unit to the wireless device, the radio resourcecontrol message.
 2. The method of claim 1, further comprising:configuring, by the base station distributed unit, the at least onefirst cell for the first logical channel and the at least one secondcell for the second logical channel.
 3. The method of claim 1, whereinthe radio resource control message further comprises a radio resourcecontrol reconfiguration message.
 4. The method of claim 1, wherein theat least one second cell is different from the at least one first cell.5. The method of claim 1, further comprising: sending, by the basestation distributed unit to the base station central unit via a firsttunnel for the first logical channel, first transport blocks; andsending, by the base station distributed unit to the base stationcentral unit via a second tunnel for the second logical channel, secondtransport blocks.
 6. The method of claim 1, wherein the messagecomprises a second message, and wherein the method further comprises:receiving, by the base station distributed unit from the base stationcentral unit, a first message comprising bearer configuration parametersassociated with a bearer for the wireless device, wherein the bearerconfiguration parameters comprise: an indication that packet duplicationis configured for the bearer; the at least one first cell index of theat least one first cell for the first logical channel; and the at leastone second cell index of the at least one second cell for the secondlogical channel.
 7. The method of claim 6, wherein the first messagefurther comprises: a first tunnel endpoint identifier of a first tunnelfor the first logical channel; and a second tunnel endpoint identifierof a second tunnel for the second logical channel.
 8. The method ofclaim 6, wherein the first message further comprises at least one of: afirst information element indicating that the first logical channelcomprises a default logical channel of the bearer; or a secondinformation element indicating that the second logical channel is forduplicated packets of the bearer.
 9. The method of claim 1, wherein thesecond logical channel is for packet duplication of packet dataconvergence protocol (PDCP) packets associated with the first logicalchannel, and wherein the message further comprises an indication that abearer for the wireless device is configured by the base stationdistributed unit.
 10. A method comprising: receiving, by a base stationcentral unit from a base station distributed unit, a message comprising:at least one first cell index of at least one first cell for a firstlogical channel; and at least one second cell index of at least onesecond cell for a second logical channel, wherein the second logicalchannel is for packet duplication associated with the first logicalchannel; and sending, by the base station central unit to a wirelessdevice via the base station distributed unit, a radio resource controlmessage comprising configuration parameters for the wireless device,wherein the configuration parameters comprise: the at least one firstcell index of the at least one first cell for the first logical channel;and the at least one second cell index of the at least one second cellfor the second logical channel.
 11. The method of claim 10, wherein theradio resource control message further comprises a radio resourcecontrol reconfiguration message.
 12. The method of claim 10, wherein theat least one second cell is different from the at least one first cell.13. The method of claim 10, further comprising: receiving, by the basestation central unit from the base station distributed unit via a firsttunnel for the first logical channel, first transport blocks; andreceiving, by the base station central unit from the base stationdistributed unit via a second tunnel for the second logical channel,second transport blocks.
 14. The method of claim 10, further comprising:receiving, by the base station central unit from the wireless device, atleast one measurement report comprising measurement results of the atleast one first cell or of the at least one second cell, wherein themeasurement results comprise at least one of: a reference signalreceived power; or a reference signal received quality; and determining,by the base station central unit and based on the at least onemeasurement report, packet duplication for a bearer for the wirelessdevice.
 15. The method of claim 10, wherein the message comprises asecond message, and wherein the method further comprises: determining,by the base station central unit, whether packet duplication isconfigured for a bearer for the wireless device; and sending, by thebase station central unit to the base station distributed unit, a firstmessage comprising bearer configuration parameters associated with thebearer for the wireless device, wherein the bearer configurationparameters comprise: an indication that the packet duplication isconfigured for the bearer; the at least one first cell index of the atleast one first cell for the first logical channel; and the at least onesecond cell index of the at least one second cell for the second logicalchannel.
 16. The method of claim 15, wherein the first message furthercomprises at least one of: a first information element indicating thatthe first logical channel comprises a default logical channel of thebearer; or a second information element indicating that the secondlogical channel is for duplicated packets of the bearer.
 17. The methodof claim 15, wherein the first message further comprises: a first tunnelendpoint identifier of a first tunnel for the first logical channel; anda second tunnel endpoint identifier of a second tunnel for the secondlogical channel.
 18. The method of claim 10, wherein the second logicalchannel is for packet duplication of packet data convergence protocol(PDCP) packets associated with the first logical channel, and whereinthe message further comprises an indication that a bearer for thewireless device is configured by the base station distributed unit. 19.A base station distributed unit comprising: one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the base station distributed unit to: send, to a basestation central unit, a message comprising: at least one first cellindex of at least one first cell for a first logical channel; and atleast one second cell index of at least one second cell for a secondlogical channel, wherein the second logical channel is for packetduplication associated with the first logical channel; receive, from thebase station central unit, a radio resource control message comprisingconfiguration parameters for a wireless device, wherein theconfiguration parameters comprise: the at least one first cell index ofthe at least one first cell for the first logical channel; and the atleast one second cell index of the at least one second cell for thesecond logical channel; and send, to the wireless device, the radioresource control message.
 20. The base station distributed unit of claim19, wherein the instructions, when executed by the one or moreprocessors, further cause the base station distributed unit to:configure the at least one first cell for the first logical channel andthe at least one second cell for the second logical channel.
 21. Thebase station distributed unit of claim 19, wherein the radio resourcecontrol message further comprises a radio resource controlreconfiguration message.
 22. The base station distributed of claim 19,wherein the at least one second cell is different from the at least onefirst cell.
 23. The base station distributed unit of claim 19, whereinthe instructions, when executed by the one or more processors, furthercause the base station distributed unit to: send, to the base stationcentral unit via a first tunnel for the first logical channel, firsttransport blocks; and send, to the base station central unit via asecond tunnel for the second logical channel, second transport blocks.24. The base station distributed unit of claim 19, wherein the messagecomprises a second message, and wherein the instructions, when executedby the one or more processors, further cause the base stationdistributed unit to: receive, from the base station central unit, afirst message comprising bearer configuration parameters associated witha bearer for the wireless device, wherein the bearer configurationparameters comprise: an indication that packet duplication is configuredfor the bearer; the at least one first cell index of the at least onefirst cell for the first logical channel; and the at least one secondcell index of the at least one second cell for the second logicalchannel.
 25. The base station distributed unit of claim 24, wherein thefirst message further comprises: a first tunnel endpoint identifier of afirst tunnel for the first logical channel; and a second tunnel endpointidentifier of a second tunnel for the second logical channel.
 26. Thebase station distributed unit of claim 24, wherein the first messagefurther comprises at least one of: a first information elementindicating that the first logical channel comprises a default logicalchannel of the bearer; or a second information element indicating thatthe second logical channel is for duplicated packets of the bearer. 27.The base station distributed unit of claim 19, wherein the secondlogical channel is for packet duplication of packet data convergenceprotocol (PDCP) packets associated with the first logical channel, andwherein the message further comprises an indication that a bearer forthe wireless device is configured by the base station distributed unit.28. A base station central unit comprising: one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the base station central unit to: receive, from a basestation distributed unit, a message comprising: at least one first cellindex of at least one first cell for a first logical channel; and atleast one second cell index of at least one second cell for a secondlogical channel, wherein the second logical channel is for packetduplication associated with the first logical channel; and send, to awireless device via the base station distributed unit, a radio resourcecontrol message comprising configuration parameters for the wirelessdevice, wherein the configuration parameters comprise: the at least onefirst cell index of the at least one first cell for the first logicalchannel; and the at least one second cell index of the at least onesecond cell for the second logical channel.
 29. The base station centralunit of claim 28, wherein the radio resource control message furthercomprises a radio resource control reconfiguration message.
 30. The basestation central unit of claim 28, wherein the at least one second cellis different from the at least one first cell.
 31. The base stationcentral unit of claim 28, wherein the instructions, when executed by theone or more processors, further cause the base station central unit to:receive, from the base station distributed unit via a first tunnel forthe first logical channel, first transport blocks; and receive, from thebase station distributed unit via a second tunnel for the second logicalchannel, second transport blocks.
 32. The base station central unit ofclaim 28, wherein the instructions, when executed by the one or moreprocessors, further cause the base station central unit to: receive,from the wireless device, at least one measurement report comprisingmeasurement results of the at least one first cell or of the at leastone second cell, wherein the measurement results comprise at least oneof: a reference signal received power; or a reference signal receivedquality; and determine, based on the at least one measurement report,packet duplication for a bearer for the wireless device.
 33. The basestation central unit of claim 28, wherein the message comprises a secondmessage, and wherein the instructions, when executed by the one or moreprocessors, further cause the base station central unit to: determine,whether packet duplication is configured for a bearer for the wirelessdevice; and send, to the base station distributed unit, a first messagecomprising bearer configuration parameters associated with the bearer,wherein the bearer configuration parameters comprise: an indication thatthe packet duplication is configured for the bearer; the at least onefirst cell index of the at least one first cell for the first logicalchannel; and the at least one second cell index of the at least onesecond cell for the second logical channel.
 34. The base station centralunit of claim 33, wherein the first message further comprises at leastone of: a first information element indicating that the first logicalchannel comprises a default logical channel of the bearer; or a secondinformation element indicating that the second logical channel is forduplicated packets of the bearer.
 35. The base station central unit ofclaim 33, wherein the first message further comprises: a first tunnelendpoint identifier of a first tunnel for the first logical channel; anda second tunnel endpoint identifier of a second tunnel for the secondlogical channel.
 36. The base station central unit of claim 28, whereinthe second logical channel is for packet duplication of packet dataconvergence protocol (PDCP) packets associated with the first logicalchannel, and wherein the message further comprises an indication that abearer for the wireless device is configured by the base stationdistributed unit.